ThinkPHP lang parameter LFI to RCE
CVE-2022-47945 affects ThinkPHP Framework before 6.0.14. When the language pack feature is enabled (lang_switch_on=true), the framework improperly handles the lang parameter, allowing an unauthenticated remote attacker to trigger local file inclusion. By causing the application to include attacker-chosen local files, exploitation can be escalated to arbitrary operating system command execution, as demonstrated through inclusion of pearcmd.php. The issue is therefore an LFI in the language-switching mechanism that can become full remote code execution in exposed deployments.
Are you exposed to this one?
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
Recent activity
12 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A ThinkPHP remote code execution vulnerability mentioned as part of the same mass-scanning infrastructure's multi-exploit playbook.
ThinkPHP local file inclusion vulnerability targeted in the campaign’s CVE scanning.
A remote code execution vulnerability in ThinkPHP that is being actively exploited in large-scale cryptomining campaigns.
A local file inclusion vulnerability in the ThinkPHP Framework that is being heavily targeted in large-scale cryptomining campaigns.
The version that knows your environment.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.