# CVE-2024-47612: XSS in Special:DataDump when displaying dump status

> An attacker with interface editing rights can inject malicious scripts into DataDump status messages, affecting users viewing the dump page.

- **Severity:** Low 3.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/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:** 2 Oct 2024
- **Updated:** 2 Oct 2024
- **Also known as:** GHSA-h8x8-24c7-r2rj

## What is CVE-2024-47612?

CVE-2024-47612 is a low-severity cross-site scripting vulnerability in miraheze DataDump, published on 2 Oct 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

DataDump is a MediaWiki extension that provides dumps of wikis. Several interface messages are unescaped (more specifically, (datadump-table-column-queued), (datadump-table-column-in-progress), (datadump-table-column-completed), (datadump-table-column-failed)). If these messages are edited (which requires the (editinterface) right by default), anyone who can view Special:DataDump (which requires the (view-dump) right by default) can be XSSed. This vulnerability is fixed with 601688ee8e8808a23b102fa305b178f27cbd226d.

Weakness: CWE-80 (Improper Neutralization of Script-Related HTML Tags in a Web Page), CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2024-47612 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-47612 is a low-severity cross-site scripting vulnerability in miraheze DataDump, published on 2 Oct 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-47612 in the wild and no public exploit code.

Affected product: miraheze DataDump. 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-47612/ (Markdown: https://insights.sbomify.com/CVE-2024-47612/index.md)
```

## Sources

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

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