CVE-2019-9082
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThinkPHP before 3.2.4, as used in Open Source BMS v1.1.1 and other products, allows Remote Command Execution via public//?s=index/\think\app/invokefunction&function=call_user_func_array&vars[0]=system&vars[1][]= followed by the command.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThinkPHP before 3.2.4 contains a Remote Command Execution vulnerability in its think\app module. Attackers can invoke arbitrary functions via the invokefunction endpoint, allowing execution of system commands without authentication by passing 'system' as the function and commands as parameters.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 3.2.4= 1.1.1= 1.6.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify ThinkPHP versionCheck the ThinkPHP version file (typically Version.php in the ThinkPHP directory) or the composer.json file for the 'version' or 'thinkphp' package version entryAffected if The installed version is lower than 3.2.4 (e.g., 3.2.3, 3.2.2, etc.)
-
Locate the application entry pointFind the public/index.php or index.php file that serves as the web entry point for the applicationAffected if The entry point file exists and the application is accessible via web
-
Verify think\app module is loadedCheck the application configuration file (typically Application/Common/Conf/config.php or similar) for 'url_route_on' or module configuration that enables the think\app module or route dispatchingAffected if URL routing is enabled and the application processes module-based requests
-
Check for vulnerable endpoint accessibilityTest access to the invokefunction endpoint by making a GET or POST request to index.php (or public/index.php) with the query string containing 's=/app/invokefunction' or similar path patterns that route to the think\app componentAffected if The server responds to requests targeting the app module (returns any status code other than 404)
-
Confirm vulnerable parameter patternInspect HTTP request handling for the 'vars' parameter - the vulnerability specifically uses vars[1] with call_user_func_array to execute commands. Check if application accepts arrays in query parametersAffected if The application accepts and processes array-style parameters (vars[0], vars[1], etc.) through the request parsing
The environment is affected if ThinkPHP version is below 3.2.4 (or if using Open Source BMS 1.1.1 or Zzzcms 1.6.1) AND the think\app module is accessible and processes the invokefunction endpoint with array-based parameters.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped3.2.4
Upgrade ThinkPHP to version 3.2.4 or later. If immediate upgrade is not feasible, restrict access to the vulnerable endpoint via web server configuration or implement IP-based filtering at the network perimeter.
ThinkPHP 3.2.4
- 1. Backup your current application and database before proceeding with any upgrade.
- 2. Identify all instances of ThinkPHP in your application (direct usage and dependencies).
- 3. Upgrade ThinkPHP framework to version 3.2.4 or later by updating the framework files or composer dependencies.
- 4. For Open Source Background Management System v1.1.1: Ensure the underlying ThinkPHP is updated to 3.2.4+ as the vulnerability exists in the framework, not the BMS itself.
- 5. For Zzzphp v1.6.1: Update the bundled ThinkPHP framework to version 3.2.4+ or check if the vendor has released a patched version.
- 6. After upgrade, verify the application functions correctly and test that the vulnerable URL pattern no longer executes arbitrary commands.
- 7. Review application logs for any indicators of compromise prior to patching.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-9082 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-9082 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data