The WordPress plugin is-human <= v1.4.2 contains an eval injection vulnerability in /is-human/engine.php that can be triggered via the 'type' parameter when the 'action' parameter is set to 'log-reset'. The root cause is unsafe use of eval() on user-controlled input, which can lead to execution of attacker-supplied PHP and OS commands. This may result in arbitrary code execution as the webserver user, site compromise, or data exfiltration. The is-human plugin was made defunct in June 2008 and is no longer available for download. This vulnerability was exploited in the wild in March 2012.
Security readout for executives and security teams
Plain-English summary
This is a critical issue in a long-defunct WordPress anti-bot plugin. If the obsolete is-human plugin remains installed, an unauthenticated attacker could run code on the server, potentially taking over the site or stealing data.
Executive priority
Prioritize immediate investigation where legacy WordPress estates exist. The business risk is full website compromise, but exposure should be narrow unless obsolete plugins were retained through migrations or backups.
Technical view
CVE-2011-10033 is an eval injection flaw in is-human plugin versions up to 1.4.2. The vulnerable path is /is-human/engine.php, where user-controlled input can reach eval() when action is log-reset, enabling remote code execution as the webserver user.
Likely exposure
Likely limited to old WordPress sites that still carry the defunct is-human plugin. The source bundle says the plugin became defunct in June 2008 and is no longer available for download.
Exploitation context
The bundle cites historical in-the-wild exploitation in March 2012 and public exploit references. It does not show current active exploitation or CISA KEV listing, so treat active exploitation status as unconfirmed.
Researcher notes
Evidence supports unauthenticated network RCE through unsafe eval() on user input. Affected-product metadata in the bundle is sparse and inconsistent, so validate exposure by filesystem and WordPress inventory rather than CPE matching alone.
Mitigation direction
Inventory WordPress sites for the is-human plugin.
If present, remove or disable the unsupported plugin after change review.
Check vendor, CVE, or hosting guidance; no patch is identified in the bundle.
Restore from clean backups if compromise indicators are found.
Harden WordPress file permissions and reduce webserver write access.
Validation and detection
Confirm whether /wp-content/plugins/is-human/ exists on WordPress hosts.
Identify any installed is-human version at or below 1.4.2.
Review web logs for requests to /is-human/engine.php using log-reset behavior.
Check for unexpected PHP files, modified plugin files, or webserver-owned artifacts.
Review host telemetry for suspicious activity under the webserver user.
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-95: 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.
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.
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
3Timeline events
1ADP providers
6Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: total
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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-95 · source CWE mapping
Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection')
Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.