CVE-2026-25366
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 · uneditedImproper Control of Generation of Code ('Code Injection') vulnerability in Themeisle Woody ad snippets insert-php allows Code Injection.This issue affects Woody ad snippets: from n/a through <= 2.7.1.
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 · moderate confidenceA Code Injection vulnerability exists in the Themeisle Woody ad snippets (insert-php) WordPress plugin versions through 2.7.1. The vulnerability allows attackers to inject and execute arbitrary PHP code on the server, potentially leading to complete site compromise, data theft, or malware deployment.
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 checksWork through these to decide whether this CVE applies to you.
-
Verify Woody ad snippets plugin is installedLog in to WordPress admin dashboard, navigate to Plugins > Installed Plugins, and look for 'Woody ad snippets' in the list of active plugins.Affected if The plugin appears in the installed plugins list and is activated.
-
Determine plugin versionIn the Plugins list, click on 'Woody ad snippets' to view the plugin details, or check the plugin file header in wp-content/plugins/woody-ad-snippets/includes/plugin.php for the Version comment.Affected if The installed version matches any version prior to the patched release (compare against the vendor's security advisory for the fixed version number).
-
Confirm insert-php feature is activeNavigate to the plugin settings in WordPress admin (Woody ad snippets > Snippets) and check if any snippets with PHP code are present, or inspect the wp_woody_snippets postmeta table in the database for postmeta_key values containing 'php_code' or similar.Affected if PHP snippets exist in the plugin or the insert-php feature is enabled in the plugin settings.
-
Inspect for unauthorized PHP code injectionAccess the WordPress database via phpMyAdmin or command line, query the wp_posts table for posts with post_type 'woody_snippet' and examine the post_content field for suspicious or unknown PHP code blocks.Affected if The post_content contains unfamiliar or malicious PHP code that was not authored by legitimate administrators.
A user is affected if the Woody ad snippets plugin with insert-php functionality is installed and the version is prior to the vendor's patched release, or if unauthorized PHP code is found in the snippet database records.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpdate Woody ad snippets to the latest patched version immediately. If no patch is available, disable the plugin, revoke administrative access from untrusted users, and review server access logs for signs of exploitation.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-25366 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-25366 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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