# CVE-2024-42758: Cross-site scripting in n/a

> Attackers can inject stored XSS payloads via page editing in the DokuWiki indexmenu plugin, potentially executing scripts in victim browsers.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/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:** 16 Aug 2024
- **Updated:** 19 Aug 2024
- **Also known as:** GHSA-c4j6-mvfp-j4wx

## What is CVE-2024-42758?

CVE-2024-42758 is a medium-severity cross-site scripting vulnerability in n/a, published on 16 Aug 2024. 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

A Cross-site Scripting (XSS) vulnerability exists in version v2024-01-05 of the indexmenu plugin when is used and enabled in Dokuwiki (Open Source Wiki Engine). A malicious attacker can input XSS payloads for example when creating or editing existing page, to trigger the XSS on Dokuwiki, which is then stored in .txt file (due to nature of how Dokuwiki is designed), which presents stored XSS.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2024-42758 being exploited?

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

Public exploit code:

- CVE-2024-42758 - Dokuwiki (indexmenu plugin) - XSS Vulnerability (github_poc): https://github.com/1s1ldur/CVE-2024-42758

## Fix prompt for AI coding agents

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

What it is: CVE-2024-42758 is a medium-severity cross-site scripting vulnerability in n/a, published on 16 Aug 2024. An attacker can exploit it over the internet without logging in, 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-42758 exists.

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

## Sources

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

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