WordPress vulnerability database

Every CVE published for WordPress core, plugins and themes since January 2024: 29,070 vulnerabilities, 1,395 of them in the last 30 days. The list is updated every day from the CVE List.

Severity is the CVSS 3.1 base score. Select a band to list only those. Last updated October 6, 2026.

Showing 1–5 of 5 vulnerabilities matching your filters

Known WordPress vulnerabilities, page 1 of 1
Severity Component Vulnerability Affected versions Published CVE Source
4.3 Medium Notification for Telegram Plugin notification-for-telegram Broken Access Control Missing Authorization to Authenticated (Subscriber+) Cron Modification via nftb_cron_action_set AJAX Action ≤ 3.5.1 CVE-2026-7620 Wordfence
4.3 Medium Notification for Telegram Plugin notification-for-telegram Broken Access Control ≤ 3.5.1 CVE-2025-62993 Patchstack
4.3 Medium Notification for Telegram Plugin notification-for-telegram Cross-Site Request Forgery No login needed ≤ 3.5 CVE-2025-58794 Patchstack
5.3 Medium Order Notification for Telegram Plugin order-notification-for-telegram Broken Access Control Missing Authorization to Unauthenticated Send Telegram Test Message No login needed ≤ 1.0.1 CVE-2024-9686 Wordfence
4.3 Medium Notification for Telegram Plugin notification-for-telegram Broken Access Control Missing Authorization to Authenticated (Subscriber+) Send Telegram Test Message ≤ 3.3.1 CVE-2024-9685 Wordfence

About this data

Where it comes from
Each row is a record from the CVE List, published by the organization that handled the report: most often Wordfence, Patchstack or WPScan. The CVE ID links to that publisher's advisory.
What is included
CVEs published since January 1, 2024 for WordPress core, plugins and themes, premium ones included. Vulnerabilities that never received a CVE ID are not listed, and rejected CVEs are removed.
Severity
The CVSS 3.1 base score set by the publisher, or by CISA when the publisher gave none. "No login needed" means the score assumes an attacker without an account.
Affected versions
The range the publisher marked as vulnerable. When the record also names the first fixed release, it is shown under the range. If your version is newer than every affected one, that CVE does not apply to you.
Updates
Every day, after the CVE List publishes its end-of-day changes.

This website uses cookies to enhance your browsing experience and ensure the site functions properly. By continuing to use this site, you acknowledge and accept our use of cookies.

Accept All Accept Required Only