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
| Severity | Component | Vulnerability | Affected versions | Published | CVE | Source |
|---|---|---|---|---|---|---|
| 9.8 Critical | Hummingbird – Speed Optimization, Caching, Minify, Compress & CDN | Remote Code Execution Speed Optimization, Caching, Minify, Compress & CDN <= 3.21.0 - Unauthenticated Remote Code Execution via Cookie Name in Page Cache Debug Log No login needed |
≤ 3.21.0 |
CVE-2026-83627 |
Wordfence | |
| 9.9 Critical | WatchMan-Site7 | Remote Code Execution Subscriber+ RCE via Debug Console |
3.1.1 – 4.2.0 |
CVE-2026-77009 |
WPScan | |
| 9.8 Critical | WP Email Debug | Broken Access Control Missing Authorization to Unauthenticated Privilege Escalation via Password Reset No login needed |
1.0 – 1.1.0 |
CVE-2025-5486 |
Wordfence | |
| 10.0 Critical | Debug Tool | Remote Code Execution No login needed |
≤ 2.2 |
CVE-2024-52416 |
Patchstack | |
| 9.8 Critical | Debug Tool | Broken Access Control Unauthenticated Arbitrary File Creation No login needed |
≤ 2.2 |
CVE-2024-10586 |
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.
CVE® records are © The MITRE Corporation and used under the CVE Terms of Use. CVE is a registered trademark of The MITRE Corporation.