# CVE-2024-29338: Cross-Site Request Forgery in Anchor CMS

> An attacker can trick authenticated users into deleting categories in Anchor CMS via a Cross-Site Request Forgery vulnerability.

- **Severity:** Low 2.4 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 22 Mar 2024
- **Updated:** 26 Aug 2024
- **Also known as:** GHSA-2whx-ccr7-fxqm

## What is CVE-2024-29338?

CVE-2024-29338 is a low-severity vulnerability in n/a, published on 22 Mar 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Anchor CMS v0.12.7 was discovered to contain a Cross-Site Request Forgery (CSRF) via /anchor/admin/categories/delete/2.

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

## Which versions are affected by CVE-2024-29338?

2 open source packages ship an affected version, including anchorcms/anchor-cms. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `anchorcms/anchor-cms` | Packagist | All versions to 0.12.7 | None |
| `anchorcms/anchor-cms` | Packagist | All versions to 0.12.7 | None |

Products: Anchorcms Anchor Cms.

## How do I fix CVE-2024-29338?

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

## Is CVE-2024-29338 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-29338 exists.

## Other vulnerabilities in n/a

- [CVE-2024-37732](https://insights.sbomify.com/CVE-2024-37732/): Cross-site scripting in n/a (high 8.8)
- [CVE-2020-23342](https://insights.sbomify.com/CVE-2020-23342/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2015-5687](https://insights.sbomify.com/CVE-2015-5687/): Deserialization in n/a (high 7.5)
- [CVE-2024-29499](https://insights.sbomify.com/CVE-2024-29499/): Cross-Site Request Forgery in Anchor CMS (high 7.4)
- [CVE-2021-44116](https://insights.sbomify.com/CVE-2021-44116/): Cross-site Scripting in Anchor CMS (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-29338 and fix it if it is affected.

What it is: CVE-2024-29338 is a low-severity vulnerability in n/a, published on 22 Mar 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-29338 exists.

Affected packages and fixed versions:
- anchorcms/anchor-cms (Packagist): affected all versions up to 0.12.7; no fix listed
- anchorcms/anchor-cms (Packagist): affected all versions up to 0.12.7; no fix listed

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

## Sources

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

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