WooThemes WooFramework < 5.3.10 - Remote Code Execution via Shortcodes
Strategic Overview
- Status
- Patched in 1.3.2
- Affected Theme
- Wootique
- Affected Version
<= 1.3.1- CVSS
- 9.8Critical
- Weakness type
- CWE-94 · Improper Control of Generation of Code ('Code Injection')
- CVE
CVE pending
At a glance
This record tracks a critical-severity Improper Control of Generation of Code ('Code Injection') vulnerability in the Wootique WordPress theme, affecting versions <= 1.3.1. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 1.3.2; sites on affected versions should update now. Disclosed April 2012, reported by Jason Gill.
Vulnerability Overview
The WooFramework, used for all WooThemes for WordPress, is vulnerable to Remote Code Execution in versions up to, and including, 5.3.9 via the shortcode preview feature. This makes it possible for unauthenticated attackers attackers 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 privileges on the target site, 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 Wootique <= 1.3.1 takes a caller who can reach the endpoint. 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 Wootique the fix is 1.3.2: builds <= 1.3.1 are affected, anything from 1.3.2 onward is not.
Remediation
Update to version 1.3.2, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Wootique: 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: Wootique 1.3.2 closes this, and updating the theme is the step that ends it.
- Firewall
- Scanner
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C