dbcve.org
Code InjectionWeakness · CWE-94

CVE-2026-8832

HIGH · 8.8 CVSS v3.1 Published 2026-05-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The WPCode WordPress plugin registers a custom 'wpcode' post type without custom capability_type or capability restrictions, causing WordPress to fall back to standard post capabilities. This allows authenticated attackers with author-level access to create executable PHP snippet posts via XML-RPC wp.newPost, which are then executed server-side via eval() in the run_eval() function when rendered through the [wpcode] shortcode.

MitigationUpdate WPCode to a patched version when available; alternatively, disable XML-RPC functionality or restrict author-level user capabilities until a fix is applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check WPCode plugin version
    Inspect the plugin file (wpcode.php header) or query the WordPress plugins API to determine the installed version of the WPCode plugin
    Affected if The installed version is 2.3.5 or lower
  2. Verify XML-RPC is enabled
    Access the XML-RPC endpoint (xmlrpc.php) or check the WordPress settings under Settings > Writing for 'XML-RPC' or inspect the site HTTP response headers for xmlrpc.php
    Affected if XML-RPC is enabled and accessible on the site
  3. Identify users with author-level access or higher
    Query the WordPress users table or use wp_users/wp_usermeta to list all users with roles of author, editor, administrator, or any custom role with post creation capabilities
    Affected if There exists at least one user account with author-level or higher access
  4. Search for existing wpcode custom post type entries
    Query the WordPress posts table for post_type='wpcode' entries, or use WP_Query to retrieve all posts of the 'wpcode' custom post type
    Affected if Any posts of type 'wpcode' exist in the database
  5. Detect shortcode usage in content
    Search the wp_posts table for content containing the [wpcode] shortcode pattern, or use a WordPress search plugin to find shortcode instances across all post content
    Affected if The [wpcode] shortcode is present in any published content

A site is affected if WPCode version 2.3.5 or lower is installed, XML-RPC is enabled, users with author-level access exist, and the wpcode custom post type or shortcode is in use.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update WPCode to a patched version when available; alternatively, disable XML-RPC functionality or restrict author-level user capabilities until a fix is applied.

Recommended fix Moderate confidence

Latest version on WordPress plugin repository (newer than 2.3.5)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the WPCode plugin
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, download the latest version from plugins.trac.wordpress.org and upload it manually via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the plugin is active and functioning correctly

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-8832 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-8832 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data