dbcve.org
Code InjectionWeakness · CWE-94

CVE-2025-13035

HIGH · 8.0 CVSS v3.1 Published 2025-11-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable

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 Code Snippets plugin for WordPress is vulnerable to PHP Code Injection in all versions up to, and including, 3.9.1. This is due to the plugin's use of extract() on attacker-controlled shortcode attributes within the `evaluate_shortcode_from_flat_file` method, which can be used to overwrite the `$filepath` variable and subsequently passed to require_once. This makes it possible for authenticated attackers, with Contributor-level access and above, to execute arbitrary PHP code on the server via the `[code_snippet]` shortcode using PHP filter chains granted they can trick an administrator into enabling the "Enable file-based execution" setting and creating at least one active Content snippet.

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 Code Snippets WordPress plugin uses extract() on shortcode attributes in the evaluate_shortcode_from_flat_file method, allowing authenticated Contributors to overwrite the $filepath variable which is then passed to require_once, enabling arbitrary PHP code execution via PHP filter chains in the [code_snippet] shortcode.

MitigationUpdate the plugin to version 3.9.2 or later, and immediately disable the 'Enable file-based execution' setting in the plugin configuration as it is required for exploitation.

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
High
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/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. Verify Code Snippets plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Code Snippets' in the list. Note the version number displayed.
    Affected if The plugin is installed and the version is less than 3.9.2 (the version is shown next to the plugin name)
  2. Confirm plugin version is vulnerable
    Compare the installed version number against 3.9.2. Versions prior to 3.9.2 contain the vulnerability.
    Affected if Installed version is lower than 3.9.2 (e.g., 3.9.1, 3.9.0, 3.8.x, etc.)
  3. Check if file-based execution is enabled
    Navigate to Snippets > Settings > General (or similar path depending on plugin version). Look for a setting labeled 'Enable file-based execution' or 'Allow file-based snippet execution'. Determine if it is turned ON or toggled to enabled.
    Affected if The 'Enable file-based execution' setting is enabled/turned on
  4. Verify shortcode is accessible to low-privileged users
    Check WordPress user roles. Navigate to Users > All Users and identify any accounts with the 'Contributor' role or higher (Editor, Author, Administrator). The [code_snippet] shortcode must be usable by these roles.
    Affected if There are user accounts with Contributor, Editor, Author, or Administrator roles who can create or edit code snippets
  5. Confirm shortcode is in active use
    Review published posts, pages, or widget areas for usage of the [code_snippet] shortcode. Check content editor views or search the database for posts containing the shortcode string.
    Affected if The [code_snippet] shortcode is actively used on the site (posts, pages, or widgets)

You are affected if the Code Snippets plugin version is below 3.9.2, the 'Enable file-based execution' setting is enabled, and users with Contributor-level access or higher exist on the site who can access the vulnerable shortcode.

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 the plugin to version 3.9.2 or later, and immediately disable the 'Enable file-based execution' setting in the plugin configuration as it is required for exploitation.

Recommended fix Moderate confidence

Code Snippets plugin version 3.9.2 or later

  1. 1. Navigate to the WordPress admin dashboard and go to Plugins > Installed Plugins
  2. 2. Locate the Code Snippets plugin in the list
  3. 3. Check the current version installed (should be 3.9.1 or earlier if vulnerable)
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. 5. Verify the update completed successfully by confirming the new version number
  6. 6. As a security best practice, review the 'Enable file-based execution' setting (Snippets > Settings > General) and ensure it remains disabled unless explicitly required, as this setting was part of the attack vector

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-13035 — 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-2025-13035 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