Wpcomplete
8 CVEs tracked. None of them is in CISA KEV.
This hub aggregates every CVE we track for Wpcomplete, a product in the web cms plugins space. Use it to gauge the current risk picture and drill into individual advisories.
Wpcomplete CVEs per month
| Month | CVEs |
|---|---|
| 2024-10 | 0 |
| 2024-11 | 0 |
| 2024-12 | 0 |
| 2025-01 | 0 |
| 2025-02 | 0 |
| 2025-03 | 0 |
| 2025-04 | 0 |
| 2025-05 | 0 |
| 2025-06 | 1 |
| 2025-07 | 0 |
| 2025-08 | 0 |
| 2025-09 | 1 |
| 2025-10 | 1 |
| 2025-11 | 0 |
| 2025-12 | 0 |
| 2026-01 | 0 |
| 2026-02 | 0 |
| 2026-03 | 0 |
| 2026-04 | 0 |
| 2026-05 | 1 |
| 2026-06 | 1 |
| 2026-07 | 0 |
| 2026-08 | 1 |
| 2026-09 | 1 |
Severity
How the 8 CVEs score on CVSS. Severity is not exploitation: KEV is counted above.
- High2
- Medium6
Latest CVEs
The 8 most recently published vulnerabilities affecting Wpcomplete.
- CVE-2026-77820WPComplete <= 2.9.9.0 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'empty' Shortcode Attribute6.4
- CVE-2026-66599WordPress WPComplete plugin <= 2.9.5.6 - Cross Site Scripting (XSS) vulnerability7.1
- CVE-2026-57661WordPress WPComplete plugin <= 2.9.5.5 - Broken Access Control vulnerability5.4
- CVE-2026-42750WordPress WPComplete plugin <= 2.9.5.4 - Cross Site Scripting (XSS) vulnerability6.5
- CVE-2025-49906WordPress WPComplete plugin <= 2.9.5.3 - Broken Access Control vulnerability5.3
- CVE-2025-58974WordPress WPComplete Plugin <= 2.9.5.2 - Cross Site Scripting (XSS) Vulnerability6.5
- CVE-2025-50046WordPress WPComplete plugin <= 2.9.5 - Cross Site Scripting (XSS) Vulnerability6.5
- CVE-2022-45825WordPress WPComplete Plugin <= 2.9.4 is vulnerable to Cross Site Scripting (XSS)7.1
Product grouping is registry-driven, with AI assist and human review. How it works