CVE-2026-8832
Authenticated RCE in WPCode plugin (<=2.3.5) via unsafe post type and eval.
Is CVE-2026-8832 being exploited?
Not confirmed. CVE-2026-8832 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 1.9% probability of exploitation in the next 30 days.
How severe is CVE-2026-8832?
CVE-2026-8832 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-8832?
Yes. A fix has been recorded for CVE-2026-8832. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-8832 affect?
CVE-2026-8832 affects WordPress WPCode plugin <= 2.3.5, WordPress sites using WPCode - Insert Headers and Footers + Custom Code Snippets. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-8832?
Upgrade to latest (>=2.3.6) and review author permissions.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Auth author can publish PHP via XML-RPC; code executes server-side via eval when rendering [wpcode].
Immediate action required
- affected<= 2.3.5
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.