# CVE-2019-9082: ThinkPHP Remote Code Execution

> Attackers can execute arbitrary commands remotely via a crafted URL in ThinkPHP, requiring an upgrade to secure the application.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 3 Nov 2021 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 Feb 2019
- **Updated:** 9 Dec 2025
- **Also known as:** GHSA-qpgr-mp84-gp92

## What is CVE-2019-9082?

CVE-2019-9082 is a high-severity code injection vulnerability in n/a, published on 24 Feb 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

ThinkPHP 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.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2019-9082?

It affects 3 products.


Products: Opensourcebms Open Source Background Management System, Thinkphp Thinkphp, Zzzcms Zzzphp.

## How do I fix CVE-2019-9082?

No fix has been published for CVE-2019-9082 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 3 May 2022.

## Is CVE-2019-9082 being exploited?

Yes. Attackers have exploited CVE-2019-9082 in the wild since at least 3 Nov 2021.

Public exploit code:

- ThinkPHP Multiple PHP Injection RCEs (metasploit)
- zzzphp CMS 1.6.1 - Cross-Site Request Forgery (exploitdb)
- ThinkPHP - Multiple PHP Injection RCEs (Metasploit) (exploitdb)
- ThinkPHP < 3.2.4 - Remote Code Execution (nuclei): http/cves/2019/CVE-2019-9082.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-9082 and fix it if it is affected.

What it is: CVE-2019-9082 is a high-severity code injection vulnerability in n/a, published on 24 Feb 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: Yes. Attackers have exploited CVE-2019-9082 in the wild since at least 3 Nov 2021.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-9082/ (Markdown: https://insights.sbomify.com/CVE-2019-9082/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-9082
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-9082
- OSV: https://osv.dev/vulnerability/CVE-2019-9082

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-9082/
Summaries are generated and may contain mistakes; the official description above is the record.