PatchSiren cyber security CVE debrief
CVE-2026-66479 Liquid Web / StellarWP CVE debrief
A Cross-Site Request Forgery (CSRF) vulnerability exists in the WPComplete plugin for WordPress, allowing for Stored XSS attacks. This issue affects WPComplete versions up to and including 2.9.5.6. The vulnerability enables attackers to trick users into performing unintended actions, potentially leading to Stored XSS attacks. Defenders should assess exposure and apply patches to prevent exploitation. The CVE Program and NVD provide official records of this vulnerability, with details on the affected WPComplete plugin versions.
- Vendor
- Liquid Web / StellarWP
- Product
- WPComplete
- CVSS
- HIGH 7.1
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-10-08
- Original CVE updated
- 2026-10-08
- Advisory published
- 2026-10-08
- Advisory updated
- 2026-10-08
Who should care
Defenders responsible for WordPress installations with the WPComplete plugin should assess exposure and apply patches. This includes operators, platform administrators, vulnerability management teams, and security teams. They should prioritize verifying WPComplete plugin versions and applying patches to prevent exploitation.
Why it matters
Defenders should prioritize verifying WPComplete plugin versions and applying patches to prevent exploitation, as this vulnerability allows for Stored XSS attacks via CSRF.
- Potential for Stored XSS attacks
- Need for CSRF protection measures
- Importance of verifying plugin versions
Technical summary
The WPComplete plugin for WordPress is vulnerable to CSRF, allowing for Stored XSS attacks. This issue affects WPComplete versions up to and including 2.9.5.6. The vulnerability enables attackers to trick users into performing unintended actions, potentially leading to Stored XSS attacks. Technical details indicate a need for CSRF protection measures and verifying plugin versions.
Defensive priority
Defenders should prioritize verifying WPComplete plugin versions and applying patches to prevent exploitation.
Recommended defensive actions
- Verify WPComplete plugin version and apply patches
- Implement CSRF protection measures
- Monitor for suspicious activity
Evidence notes
The CVE Program and NVD provide official records of this vulnerability, with details on the affected WPComplete plugin versions. Evidence is based on CVE Program and NVD records. Affected versions are confirmed up to 2.9.5.6. Defenders should verify WPComplete plugin versions and apply patches. Official records indicate a CSRF vulnerability allowing Stored XSS attacks.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-66479 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-66479
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-66479 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-66479
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
WordPress WPComplete plugin <= 2.9.5.6 - CSRF to Stored XSS vulnerability
Unverified legacy reference
URL: https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/66xxx/CVE-2026-66479.json
cve_program_cvelist_v5
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.