Strategic Overview
- Status
- Unpatched
- Affected Plugin
- is-human
- Affected Version
<= 1.4.2- CVSS
- 9.8Critical
- Weakness type
- CWE-95 · Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection')
- CVE
CVE-2011-10033
At a glance
CVE-2011-10033 is a critical-severity Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection') vulnerability in the is-human WordPress plugin, affecting versions <= 1.4.2. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed May 2011, reported by neworder.
Vulnerability Overview
The is-human plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1.4.2 via the /plugins/is-human/engine.php file. This is due to the plugin accepting user-supplied input passed to eval(). This makes it possible for unauthenticated 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-95: Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection')
The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes code syntax before using the input in a dynamic evaluation call (e.g. eval).
Remediation
No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
How does WordSec protect against this?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: 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. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.
- Firewall
- Scanner
- Login Security
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C