dbcve.org
Code Snippets CptWordPress extension · Jtsternberg

CVE-2024-13895

MEDIUM · 6.3 CVSS v3.1 Published 2025-03-08
Fix available
A fix is available. Upgrade to after 2.1.0 or later.
See remediation →
69/100
Remediation priority · Elevated
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 The Code Snippets CPT plugin for WordPress is vulnerable to arbitrary shortcode execution in all versions up to, and including, 2.1.0. This is due to the software allowing users to execute an action that does not properly validate a value before running do_shortcode. This makes it possible for authenticated attackers, with Subscriber-level access and above, to execute arbitrary shortcodes.

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 CPT plugin for WordPress fails to properly validate user input before passing it to do_shortcode(), allowing authenticated users with Subscriber-level permissions to execute arbitrary shortcodes. This can lead to content injection, privilege escalation, or further compromise depending on what shortcodes are available on the site.

MitigationUpdate to version 2.1.1 or later which contains the fix. Until patched, consider restricting user registration or revoking shortcode execution capabilities from low-privilege roles.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Code Snippets CptWordPress extension
Affected:<= 2.1.0

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
Low
Integrity
Low
Availability
Low

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

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 CPT plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Code Snippets CPT' by Jtsternberg, or check the plugin files in /wp-content/plugins/ for the code-snippets-cpt directory
    Affected if Plugin is not found in the WordPress installation
  2. Determine the installed version
    In Plugins > Installed Plugins, locate the Code Snippets CPT plugin and note the version number displayed. Alternatively, check the plugin's main PHP file for the 'Version' header in the plugin comment block
    Affected if Version displayed is 2.1.0 or lower (any version up to and including 2.1.0)
  3. Confirm user registration is enabled
    In WordPress admin, go to Settings > General and check 'Membership: Anyone can register' is ticked. Also verify if any low-privilege Subscriber accounts exist under Users > All Users
    Affected if User registration is enabled OR low-privilege Subscriber accounts exist on the site

You are affected if the Code Snippets CPT plugin is installed with version 2.1.0 or lower AND attackers can obtain or already have Subscriber-level access to your WordPress site.

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
Upgrade available Upgrade to a release after 2.1.0
Interim mitigation

Update to version 2.1.1 or later which contains the fix. Until patched, consider restricting user registration or revoking shortcode execution capabilities from low-privilege roles.

Recommended fix Moderate confidence

2.1.1 or latest stable release

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the Code Snippets CPT plugin
  4. Check if the current version is 2.1.0 or below
  5. If vulnerable, click 'Update Now' to install the latest version
  6. Alternatively, navigate to Plugins > Add New > Upload Plugin and upload the latest version from wordpress.org
  7. After update, verify the plugin version is 2.1.1 or higher

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

Fix this in Code Snippets Cpt 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 the upgrade done

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-2024-13895 — 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-2024-13895 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