Radar sectionsDatabase
Check my site
WordPress plugin

WPCode <= 2.3.5 — Authenticated (Author+) Remote Code Execution via CPT Capability Bypass via XML-RPC wp.newPost

CVE-2026-8832Published · Updated

Action summary

Affected: ≤2.3.5Update to 2.3.6 or newer

All remediation steps
Severity
High8.8
CVSS
8.8
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
What does this vector mean?
AV:N Attack vector
Network
AC:L Attack complexity
Low
PR:L Privileges required
Low
UI:N User interaction
None
S:U Scope
Unchanged
C:H Confidentiality
High
I:H Integrity
High
A:H Availability
High
Weakness
CWE-94 Improper Control of Generation of Code
Required access
Unknown
Exploit prediction (EPSS)
No score
CISA KEV
Not listed

Am I affected?

WPCode – Insert Headers and Footers + Custom Code Snippets – WordPress Code Manager insert-headers-and-footers

  1. Affected≤ 2.3.5
  2. Patched in2.3.6

Update to 2.3.6 or newer.

You are affected if you run ≤ 2.3.5. Version 2.3.6 and later are not affected by this issue.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under WPCode – Insert Headers and Footers + Custom Code Snippets – WordPress Code Manager.
  • No admin access? Run a passive check of your site. It reads public files only.

What to do

  1. Update to version 2.3.6, or a newer patched version
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch WPCode – Insert Headers and Footers + Custom Code Snippets – WordPress Code Manager to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to Win3.

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.

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

More in WPCode – Insert Headers and Footers + Custom Code Snippets – WordPress Code Manager

All 5
More vulnerabilities in WPCode – Insert Headers and Footers + Custom Code Snippets – WordPress Code Manager
SeverityVulnerabilityCVEPublished
High7.3Unauthenticated Snippet Safe Mode Bypass
<2.4.0Update to 2.4.0
CVE-2026-101301
Medium6.1Unauthenticated Reflected Cross-Site Scripting via Tag Filter Links
≤2.0.13Update to 2.0.13.1
CVE-2023-3524
Medium4.7Cross-Site Request Forgery
≤2.0.8Update to 2.0.9
CVE-2023-1624
Medium5.4Missing Authorization to Sensitive Key Disclosure/Update
≤2.0.6Update to 2.0.7
CVE-2023-0328

Timeline

  1. CVE published

    Severity high, CVSS 8.8

  2. Record last updated

Sources & licenses

Wordfence record
Vulnerability data
Wordfence Intelligence. Copyright 2012-2026 Defiant Inc. Licensed under the CC BY-SA 4.0.
CVE® identifiers
Copyright 1999-2026 The MITRE Corporation. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Are you sure?