# CVE-2019-9182: Cross-site request forgery in n/a

> A CSRF vulnerability in ZZZCMS allows attackers to inject PHP code by tricking admins into submitting malicious file edits.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 26 Feb 2019
- **Updated:** 9 Dec 2025
- **Also known as:** GHSA-82gq-xhgq-4fqw

## What is CVE-2019-9182?

CVE-2019-9182 is a high-severity vulnerability in n/a, published on 26 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

There is a CSRF in ZZZCMS zzzphp V1.6.1 via a /admin015/save.php?act=editfile request. It allows PHP code injection by providing a filename in the file parameter, and providing file content in the filetext parameter.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Zzzcms Zzzphp.

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

No fix has been published for CVE-2019-9182 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-9182 being exploited?

There is no known exploitation of CVE-2019-9182 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2022-23881](https://insights.sbomify.com/CVE-2022-23881/): Code injection in n/a (critical 9.8)
- [CVE-2021-32605](https://insights.sbomify.com/CVE-2021-32605/): Command injection in n/a (critical 9.8)
- [CVE-2020-24877](https://insights.sbomify.com/CVE-2020-24877/): SQL injection in n/a (critical 9.8)
- [CVE-2020-18717](https://insights.sbomify.com/CVE-2020-18717/): SQL injection in n/a (critical 9.8)
- [CVE-2020-20298](https://insights.sbomify.com/CVE-2020-20298/): Code injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-9182 is a high-severity vulnerability in n/a, published on 26 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: There is no known exploitation of CVE-2019-9182 in the wild and no public exploit code.

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-9182/ (Markdown: https://insights.sbomify.com/CVE-2019-9182/index.md)
```

## Sources

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

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