CVE
TopThink ThinkPHP remote code execution in PATH_INFO dispatcher
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Do first: Workaround: The checked facts describe no workaround. The only scoping they give is that 3.0 is affected only in Lite mode, and the vendor's guidance for limiting exposure should be checked directly.
Summary
ThinkPHP 2.0 through 2.2 and 3.0 Lite mode contains an eval injection vulnerability in the Dispatcher PATH_INFO parsing, which uses preg_replace with the /e modifier and a double-quoted replacement. Unauthenticated attackers can send crafted requests to index.php with a malicious 's' parameter containing PHP expressions to execute arbitrary code on the server. Exploitation evidence was first observed by the Shadowserver Foundation on 2023-10-14.
Who should check
Teams running ThinkPHP 2.0 through 2.2, or ThinkPHP 3.0 in Lite mode, on web servers that serve index.php
“Affecting ThinkPHP >= 2.0, <= 2.2”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.3/10CVSS 9.3
- No patch5/5No patch listed yet
What would change the score
- Would score about 76 if added to CISA KEV
- Would score about 71 if CISA's SSVC rates exploitation active
- Would score about 36 if advisories confirm default setups are exposed
What to do
Workaround: The checked facts describe no workaround. The only scoping they give is that 3.0 is affected only in Lite mode, and the vendor's guidance for limiting exposure should be checked directly.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2012-20007 (ThinkPHP 2.x / 3.0 Lite Unauthenticated RCE via Dispatcher PATH_INFO), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2012-20007 (entry last updated 2026-11-18):
Affected:
- TopThink ThinkPHP: from 2.0, through 2.2
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- ThinkPHP 2.0 through 2.2 or 3.0 (Lite mode) (source: https://www.vulncheck.com/advisories/thinkphp-2-x-3.0-lite-unauthenticated-rce-via-dispatcher-path-info)
- Lite mode is in use (for ThinkPHP 3.0) (source: https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/thinkphp/thinkphp-2-rce.yaml)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2012-20007 is not listed as of cve.now's last read.
This KEV status is for CVE-2012-20007 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/thinkphp/thinkphp-2-rce.yaml
- https://www.vulncheck.com/advisories/thinkphp-2-x-3.0-lite-unauthenticated-rce-via-dispatcher-path-info
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2012-20007
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2012-20007"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- TopThink ThinkPHP
From 2.0 · through 2.2
Evidence 6
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2012-20007 |
| Record | NVD · CVE-2012-20007 |
| Public exploit code 3Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub). | |
| Exploit | web.archive.org · web/20140201221754/http:/www.jb51.net:80/softjc/43550.html |
| Exploit | GitHub · vulhub/vulhub · tree/master/thinkphp/2-rce |
| Repository | GitHub · projectdiscovery/nuclei-templates · http/vulnerabilities/thinkphp/thinkphp-2-rce.yaml |
| Other links 1 | |
| Link | vulncheck.com · advisories/thinkphp-2-x-3.0-lite-unauthenticated-rce-via-dispatcher-path-info |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2012-20007
Is CVE-2012-20007 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
ThinkPHP 2.0 through 2.2 and 3.0 in Lite mode contain an eval injection flaw. PHP expressions passed in the 's' parameter are executed on the server, which allows arbitrary code execution.Source: vulncheck.com, github.com
Which versions are affected by CVE-2012-20007?
ThinkPHP: from 2.0 through 2.2.Source: cve.now feed data
Am I affected, and how do I check?
ThinkPHP 2.0 through 2.2 are in scope, and 3.0 is in scope only when Lite mode is in use. To check, look at the installed ThinkPHP version and whether Lite mode is enabled in the application.Source: vulncheck.com, github.com
How do I fix CVE-2012-20007?
The checked facts name no fixed version and no patch identifiers, so no upgrade target can be given from them. Check TopThink's advisory for a fixed release or patch before deciding what to install.Source: vulncheck.com, github.com
What if there's no patch?
The checked facts describe no workaround. The only scoping they give is that 3.0 is affected only in Lite mode, and the vendor's guidance for limiting exposure should be checked directly.Source: vulncheck.com, github.com