Skip to main content
Mallory
HighCISA KEVExploited in the wildPublic exploit

ThinkPHP Remote Command Execution via invokefunction

IdentifiersCVE-2019-9082CWE-94· Improper Control of Generation of…

CVE-2019-9082 is a remote code execution vulnerability in ThinkPHP affecting versions before 3.2.4, and has also been observed in products using the framework such as Open Source BMS v1.1.1. The issue is exploitable through crafted requests to ThinkPHP entry points such as /?s= or /index.php?s= that reach the framework's invokefunction functionality. Publicly documented exploitation uses a request like public//?s=index/\think\app/invokefunction&function=call_user_func_array&vars[0]=system&vars[1][]=<command>, allowing attacker-controlled input to invoke PHP callable functions and pass arbitrary arguments. Supporting content also references related exploit chains using the public _method=__construct gadget path in some ThinkPHP deployments. Successful exploitation results in attacker-supplied commands being executed by the underlying PHP application context.

Share:
For your environment

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.

ANALYST BRIEF

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.

An unauthenticated remote attacker can execute arbitrary system commands or PHP code on a vulnerable internet-exposed ThinkPHP application. Impact includes full compromise of the web application, arbitrary file access or modification within the web server's privileges, malware deployment, cryptominer installation, botnet enrollment, web shell placement, credential theft, and potential lateral movement depending on host configuration and privileges. The content indicates this vulnerability has been actively exploited in the wild by automated campaigns.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, restrict external access to ThinkPHP entry points, especially routes exposing /?s= or /index.php?s= request handling. Use WAF or reverse-proxy rules to block requests containing invokefunction, call_user_func_array, _method=__construct, or suspicious vars parameters associated with public exploit chains. Disable unnecessary dangerous PHP functions where operationally feasible, segment the application from sensitive internal resources, and monitor logs for exploitation attempts targeting ThinkPHP RCE patterns. Because exploitation is commonly automated, rate limiting and IP-based filtering may reduce opportunistic attacks but are not substitutes for patching.

Remediation

Patch, then assume compromise.

Upgrade ThinkPHP to a fixed release; the provided content states versions before 3.2.4 are vulnerable. In affected products that embed ThinkPHP, apply the vendor-provided update or upgrade the bundled framework to a non-vulnerable version. Validate remediation by testing both common routing patterns (/index.php?s= and /?s=) because deployments may expose either path. Review internet-facing ThinkPHP applications for signs of compromise, including unexpected command execution, dropped scripts or binaries, web shells, and follow-on malware.
PUBLIC EXPLOITS

Exploits

No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.

VALID 0 / 1 TOTALView more in app

All candidate exploits were filtered out by Mallory's validation.

EXPOSURE SURFACE

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.

VendorProductType
OpensourcebmsOpen Source Background Management Systemapplication
ThinkphpThinkphpapplication
ZzzcmsZzzphpapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence1

Every observed campaign linking this CVE to a named adversary.

Associated malware2

Malware families riding this exploit, with evidence and IOCs.

Detection signatures2

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity5

Community discussion across Reddit, Mastodon, and other social sources.