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

> Cross-site request forgery allows attackers to delete modules in Pluck CMS by tricking admins into visiting a malicious link.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N`)
- **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:** 23 Feb 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-vrw6-67xg-v5fp

## What is CVE-2019-9049?

CVE-2019-9049 is a medium-severity vulnerability in n/a, published on 23 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

An issue was discovered in Pluck 4.7.9-dev1. There is a CSRF vulnerability that can delete modules via a /admin.php?action=module_delete&var1= URI.

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

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

It affects 1 product.


Products: Pluck-Cms Pluck.

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

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

## Is CVE-2019-9049 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-43042](https://insights.sbomify.com/CVE-2024-43042/): Security feature bypass in n/a (critical 9.8)
- [CVE-2021-31746](https://insights.sbomify.com/CVE-2021-31746/): Path traversal in n/a (critical 9.8)
- [CVE-2020-20951](https://insights.sbomify.com/CVE-2020-20951/): Command injection in n/a (critical 9.8)
- [CVE-2019-11344](https://insights.sbomify.com/CVE-2019-11344/): File upload in n/a (critical 9.8)
- [CVE-2018-11736](https://insights.sbomify.com/CVE-2018-11736/): File upload in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-9049 is a medium-severity vulnerability in n/a, published on 23 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-9049 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-9049/ (Markdown: https://insights.sbomify.com/CVE-2019-9049/index.md)
```

## Sources

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

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