Woody Code Snippets – Insert PHP, CSS, JS, and Header/Footer Scripts <= 2.7.1 - Authenticated (Contributor+) Remote Code Execution
Strategic Overview
- Status
- Patched in 2.7.2
- Affected Version
<= 2.7.1- CVSS
- 8.8High
- Weakness type
- CWE-94 · Improper Control of Generation of Code ('Code Injection')
- CVE
CVE-2026-25366
At a glance
CVE-2026-25366 is a high-severity Improper Control of Generation of Code ('Code Injection') vulnerability in the Woody Code Snippets WordPress plugin, affecting versions <= 2.7.1. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 2.7.2; sites on affected versions should update now. Disclosed March 2026, reported by Nguyen Ba Khanh.
Vulnerability Overview
The Woody Code Snippets – Insert PHP, CSS, JS, and Header/Footer Scripts plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 2.7.1. This makes it possible for authenticated attackers, with Contributor-level access and above, to execute code on the server.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-94: Improper Control of Generation of Code ('Code Injection')
Reaching this weakness in Woody Code Snippets <= 2.7.1 takes an account at Contributor level or above. Code injection means input from a request reaches a language construct that evaluates code, so the attacker's text is executed rather than treated as data.
The injected code runs with the web server's privileges, giving the attacker the same access to the database and filesystem as WordPress itself. For Woody Code Snippets the fix is 2.7.2: builds <= 2.7.1 are affected, anything from 2.7.2 onward is not.
Remediation
Update to version 2.7.2, or a newer patched version
How does WordSec protect against this?
An attacker needs Contributor access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: Woody Code Snippets 2.7.2 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Woody Code Snippets – Insert PHP, CSS, JS, and Header/Footer Scripts
- 8.8CVE-2019-15858: Woody Ad Snippets <= 2.2.4 Settings Import
CVE-2019-15858 - 7.5CVE-2019-14773: Woody Ad Snippets <= 2.2.5 Arbitrary Post Deletion
CVE-2019-14773 - 6.4CVE-2019-16289: Woody Ad Snippets <= 2.2.8 Cross-Site Scripting
CVE-2019-16289 - 6.1Woody code snippets <= 2.4.5 Reflected Cross-Site Scripting
- 4.4CVE-2024-35751: Woody code snippets Stored XSS
CVE-2024-35751 - 4.3CVE-2020-36759: Woody code snippets <= 2.3.9 CSRF Bypass
CVE-2020-36759
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C