LiveActive security incident?Get immediate response
CVE Record

CVE-2026-25366: WordPress Woody ad snippets plugin <= 2.7.1 - Remote Code Execution (RCE) vulnerability

Improper 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.

CriticalCVSS 9.9Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2026-25366 is a critical code-injection issue in the WordPress Woody ad snippets plugin, package insert-php, affecting versions through 2.7.1. A logged-in attacker may be able to execute code through the plugin without user interaction, risking full site compromise.

Executive priority

Prioritize this for WordPress environments using the plugin. The issue is critical, but current sources do not confirm active exploitation. Sites running affected versions should be remediated or have the plugin disabled promptly.

Technical view

The CVE describes CWE-94 improper control of code generation in Themeisle Woody ad snippets insert-php. CVSS 3.1 is 9.9: network-accessible, low complexity, low privileges required, no user interaction, changed scope, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is limited to WordPress sites with Woody ad snippets / insert-php installed at version 2.7.1 or earlier. The CVSS vector indicates exploitation requires some authenticated privilege, not anonymous access.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Public information indicates high potential impact because successful code injection could execute server-side code in the WordPress environment.

Researcher notes

Use the description and title as the primary affected-version evidence: through 2.7.1. The provided affected metadata is inconsistent, listing version “0” while the narrative states <=2.7.1. No exploit details or fixed version are provided in the bundle.

Mitigation direction

  • Inventory WordPress sites for Woody ad snippets / insert-php installations.
  • Treat versions 2.7.1 and earlier as vulnerable.
  • Check Themeisle and Patchstack guidance for a fixed version or official remediation.
  • Disable or remove the plugin if it is not business-critical.
  • Restrict WordPress accounts and plugin-management privileges until remediated.

Validation and detection

  • Confirm whether Woody ad snippets / insert-php is installed on each WordPress site.
  • Record the installed plugin version and compare it to 2.7.1.
  • Review WordPress user roles for low-privilege accounts with plugin or snippet access.
  • Check vendor advisories for any updated affected-version or fix information.
  • Monitor logs for unusual authenticated changes to snippets or plugin settings.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-94: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-25366 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.9 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.9CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H3.16Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.9Critical
CVSS 3.1 vector shape for CVE-2026-25366Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
ThemeisleWoody ad snippetsinsert-php, 0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-94 · source CWE mapping

Improper Control of Generation of Code ('Code Injection')

Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.