# CVE-2024-5029: CM Table Of Contents – WordPress TOC Plugin < 1.2.4 - Stored XSS via CSRF

> Attackers can inject stored XSS payloads into the CM Table Of Contents plugin settings via CSRF, potentially compromising admin sessions.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/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:** 21 Nov 2024
- **Updated:** 21 Nov 2024
- **Also known as:** GHSA-26fv-px38-wm73

## What is CVE-2024-5029?

CVE-2024-5029 is a medium-severity cross-site scripting vulnerability in Unknown CM Table Of Contents, published on 21 Nov 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

The CM Table Of Contents  WordPress plugin before 1.2.4 does not have CSRF check when updating its settings, and is missing sanitisation as well as escaping, which could allow attackers to make logged in admin add Stored XSS payloads via a CSRF attack.

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

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

It affects 1 product.


Products: Cminds Cm Table of Contents.

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

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

## Is CVE-2024-5029 being exploited?

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

## Other vulnerabilities in Unknown CM Table Of Contents

- [CVE-2024-5030](https://insights.sbomify.com/CVE-2024-5030/): CM Table Of Contents – WordPress TOC Plugin < 1.2.3 - Settings Reset via CSRF (low 3.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-5029 is a medium-severity cross-site scripting vulnerability in Unknown CM Table Of Contents, published on 21 Nov 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-5029 exists.

Affected product: Unknown CM Table Of Contents. 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-2024-5029/ (Markdown: https://insights.sbomify.com/CVE-2024-5029/index.md)
```

## Sources

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

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