WPCode <= 2.3.5 - Authenticated (Author+) Remote Code Execution via CPT Capability Bypass via XML-RPC wp.newPost
Strategic Overview
- Status
- Patched in 2.3.6
- Affected Version
<= 2.3.5- CVSS
- 8.8High
- Weakness type
- CWE-94 · Improper Control of Generation of Code ('Code Injection')
- CVE
CVE-2026-8832
At a glance
CVE-2026-8832 is a high-severity Improper Control of Generation of Code ('Code Injection') vulnerability in the WPCode WordPress plugin, affecting versions <= 2.3.5. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Author level or above. The issue is fixed in version 2.3.6; sites on affected versions should update now. Disclosed May 2026, reported by Win3.
Vulnerability Overview
The WPCode - Insert Headers and Footers + Custom Code Snippets - WordPress Code Manager plugin for WordPress is vulnerable to Remote Code Execution in versions up to, and including, 2.3.5 This is due to the 'wpcode' custom post type being registered without a custom capability_type or capability restrictions in the wpcode_register_post_type() function, allowing WordPress core to fall back to standard post capabilities for all creation paths including XML-RPC. This makes it possible for authenticated attackers, with author-level access and above, to create and publish executable PHP snippet posts via XML-RPC wp.newPost, which are then executed server-side via eval() in the run_eval() function when the snippet is rendered through the [wpcode] shortcode.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-94: Improper Control of Generation of Code ('Code Injection')
WPCode <= 2.3.5 carries this weakness at wpcode, and reaching it takes an account at Author level or above. Code injection means input from a request reaches a language construct that evaluates code, so the attacker's text is executed rather than treated as data.
The injected code runs with the web server's privileges, giving the attacker the same access to the database and filesystem as WordPress itself. For WPCode the fix is 2.3.6: builds <= 2.3.5 are affected, anything from 2.3.6 onward is not.
Remediation
Update to version 2.3.6, or a newer patched version
How does WordSec protect against this?
An attacker needs Author access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: WPCode 2.3.6 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- Alerts
External References
Related records
Other vulnerabilities in WPCode – Insert Headers and Footers + Custom Code Snippets – WordPress Code Manager
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C