dbcve.org
Code InjectionWeakness · CWE-94

CVE-2024-3105

CRITICAL · 9.9 CVSS v3.1 Published 2024-06-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/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 Woody code snippets – Insert Header Footer Code, AdSense Ads plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 2.5.0 via the 'insert_php' shortcode. This is due to the plugin not restricting the usage of the functionality to high level authorized users. This makes it possible for authenticated attackers, with contributor-level access and above, to execute code on the server.

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 Woody code snippets WordPress plugin versions up to 2.5.0 contains a critical remote code execution vulnerability in its 'insert_php' shortcode functionality. The plugin fails to properly restrict the PHP execution feature to high-privilege administrators, allowing any authenticated user with contributor-level access or higher to execute arbitrary PHP code on the server through the shortcode.

MitigationUpdate the plugin to version 2.5.1 or later immediately. Until patched, disable the plugin or restrict user registrations/contributor-level access. Review server access logs for indicators of compromise and consider rotating credentials if exploitation is suspected.

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 Woody code snippets plugin is installed
    Navigate to WordPress admin > Plugins > Installed Plugins and look for 'Woody code snippets' in the list. Alternatively, check the /wp-content/plugins/ directory for the woody-ad-snippets folder.
    Affected if The plugin is present in the WordPress installation
  2. Check installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins > Woody code snippets and note the version number displayed. Compare this to the affected range (versions up to and including 2.5.0).
    Affected if The installed version is 2.5.0 or earlier
  3. Confirm insert_php shortcode is available
    Check if the plugin's PHP execution shortcode (commonly [insert_php] or similar) is being used in any posts, pages, or custom post types. Search the wp_posts table in the database for posts containing 'insert_php' shortcode tags, or use a plugin search tool.
    Affected if The insert_php shortcode is present and active in any content
  4. Review user role permissions
    In WordPress admin, go to Users > Users and identify any accounts with Contributor, Author, or Editor roles. These roles can create/edit posts containing shortcodes. Check if any untrusted users exist at these privilege levels.
    Affected if There are users with Contributor-level access or higher who should not have the ability to execute PHP code

A user is affected if the Woody code snippets plugin version is 2.5.0 or earlier AND the insert_php shortcode functionality is accessible to users with Contributor-level permissions or higher.

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 2.5.1 or later immediately. Until patched, disable the plugin or restrict user registrations/contributor-level access. Review server access logs for indicators of compromise and consider rotating credentials if exploitation is suspected.

Recommended fix High confidence

2.5.1 or latest available version

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Woody code snippets – Insert Header Footer Code, AdSense Ads' plugin
  4. If the plugin shows version 2.5.0 or below, click 'Update Now' to upgrade to version 2.5.1 or latest available version
  5. Alternatively, download the latest version from wordpress.org/plugins/ snippets-code
  6. Verify the update was successful by checking the plugin version after updating

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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