WordPress vulnerability database
Every CVE published for WordPress core, plugins and themes since January 2024: 30,513 vulnerabilities, 2,009 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 26, 2026.
Showing 1–7 of 7 vulnerabilities matching your filters
| Severity | Component | Vulnerability | Affected versions | Published | CVE | Source |
|---|---|---|---|---|---|---|
| 6.5 Medium | WP Bakery Autoresponder Addon | Broken Access Control No login needed |
≤ 1.0.6 |
CVE-2026-27362 |
Patchstack | |
| 5.9 Medium | Pondol BBS | Cross-Site Scripting |
≤ 1.1.8.4 |
CVE-2025-49336 |
Patchstack | |
| 5.4 Medium | Responder | Cross-Site Request Forgery No login needed |
≤ 4.3.8 Fixed in 4.4.0 |
CVE-2025-58801 |
Patchstack | |
| 5.4 Medium | Pixel WordPress Form BuilderPlugin & Autoresponder | Cross-Site Request Forgery No login needed |
≤ 1.0.3 Fixed in 1.0.4 |
CVE-2025-31915 |
Patchstack | |
| 6.1 Medium | PeoplePond | Cross-Site Request Forgery CSRF to Stored XSS No login needed |
≤ 1.1.9 |
CVE-2024-8085 |
WPScan | |
| 5.3 Medium | DAP to Autoresponders Email Syncing | Information Disclosure Unauthenticated Information Exposure No login needed |
≤ 1.0 |
CVE-2025-2840 |
Wordfence | |
| 4.3 Medium | Arigato Autoresponder and Newsletter | Cross-Site Request Forgery No login needed |
≤ 2.7.2.3 Fixed in 2.7.2.4 |
CVE-2024-34823 |
Patchstack |
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 attacker needs no account, as the publisher's text states it, or as the score assumes when the text does not say.
- Affected versions
- The range the publisher marked as vulnerable. When the record also names the first fixed release, it is shown under the range. Some publishers only give the last affected version; when their references show the fix, the fixed release is the first one on wordpress.org after that version. 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.