Skip to content
vulneraibility.com
Screener

CVE-2019-9082

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.

CVSS
8.8Highscored by CISA
Exploited in the wild
Yes, in CISA KEV since 3 Nov 2021CISA deadline for US federal agencies: 3 May 2022public exploit code
EPSS
97.4%chance of exploitation in the next 30 daystop 0.2% of scored CVEsFIRST score of 11 Nov 2026
Fix
Not stated by the vendorno fixed release in the CVE record
Published
24 Feb 2019analysed here 12 Nov 2026

Do first. Apply updates per vendor instructions. (CISA's required action for this KEV entry)

Summary

Triage

Attack surface
Server-side
Exploitable
At runtime
Attack vector
network
Weaknesses
Can a WAF block it?
Partly. See why

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.

Affected products

Products named in our analysis

  • thinkphp:thinkphp
  • opensourcebms:open_source_background_management_system
  • zzzcms:zzzphp

Fix and mitigation

WAF and other mitigations

Can a WAF block it? Partly. Code injection payloads are often obfuscated, so they slip past generic WAF rules.

Also consider: remove eval sinks · RASP · patch

Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog
Listed since 3 Nov 2021.
CISA due date
3 May 2022, the remediation deadline for US federal agencies
CISA required action
Apply updates per vendor instructions.
Public exploit code
Yes: 2 on Exploit-DB · 1 Metasploit module · 1 Nuclei template
CISA SSVC
exploitation active, automatable no, technical impact totalAssessed by CISA 7 Feb 2025 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.

Exploit-DB

Metasploit

Nuclei

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

Timeline

  1. 24 Feb 2019Published
  2. 4 Mar 2019First public exploit or proof of concept7 days later
  3. 3 Nov 2021Added to CISA KEV (exploited in the wild)975 days (about 3 years) later
  4. 3 May 2022CISA remediation due date (US federal agencies)181 days (about 6 months) later
  5. 7 Feb 2025CISA SSVC assessment: exploitation active1,012 days (about 3 years) later
  6. 9 Dec 2025CVE record last updated305 days (about 10 months) later
  7. 12 Nov 2026Analysed by vulneraibility.com338 days (about 11 months) later

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

MetricValueWhat it means
Attack vectorNetworkReachable over the internet or any routable network.
Attack complexityLowRepeatable attack, no special conditions.
Privileges requiredNoneThe attacker needs no prior access.
User interactionRequiredA victim must click, open or otherwise cooperate.
ScopeUnchangedImpact stays within the vulnerable component.
ConfidentialityHighTotal data disclosure possible.
IntegrityHighComplete modification possible.
AvailabilityHighFull outage possible.

Common questions

Is CVE-2019-9082 being exploited?

Yes. CVE-2019-9082 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2019-9082?

CVE-2019-9082 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2019-9082?

Not known from our data. No patch reference has been recorded for CVE-2019-9082, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2019-9082 affect?

CVE-2019-9082 affects thinkphp:thinkphp, opensourcebms:open_source_background_management_system, zzzcms:zzzphp. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVDCVE.orgCVE DetailsSource

4 references in the CVE record, grouped by the tags the record gives them.

Exploits (1)

Other links (3)

Where the data on this page comes from

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.

© 2026 vulneraibility.com