# CVE-2024-34500: MediaWiki UnlinkedWikibase Cross-site Scripting vulnerability

> Attackers can execute arbitrary scripts via unescaped error messages in the UnlinkedWikibase extension, requiring an upgrade to patched versions.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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:** Yes
- **Published:** 5 May 2024
- **Updated:** 4 Nov 2025
- **Also known as:** BIT-mediawiki-2024-34500, GHSA-wcx3-63mm-h8x6

## What is CVE-2024-34500?

CVE-2024-34500 is a medium-severity cross-site scripting vulnerability in Fedoraproject Fedora, published on 5 May 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

An issue was discovered in the UnlinkedWikibase extension in MediaWiki before 1.39.6, 1.40.x before 1.40.2, and 1.41.x before 1.41.1. XSS can occur through an interface message. Error messages (in the $err var) are not escaped before being passed to Html::rawElement() in the getError() function in the Hooks class.

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

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

3 open source packages ship an affected version, including samwilson/unlinked-wikibase and mediawiki. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `samwilson/unlinked-wikibase` | Packagist | All versions | 1.42.0 |
| `samwilson/unlinked-wikibase` | Packagist | All versions | 1.42.0 |
| `mediawiki` | Bitnami | All versions | 1.41.1 |

Products: Fedoraproject Fedora, Mediawiki Mediawiki.

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

Upgrade samwilson/unlinked-wikibase to 1.42.0 or later.

## Is CVE-2024-34500 being exploited?

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

## Other vulnerabilities in Fedoraproject Fedora

- [CVE-2024-4577](https://insights.sbomify.com/CVE-2024-4577/): PHP-CGI OS Command Injection (critical 9.8, exploited in the wild)
- [CVE-2021-39226](https://insights.sbomify.com/CVE-2021-39226/): Grafana Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2019-5544](https://insights.sbomify.com/CVE-2019-5544/): VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2024-4947](https://insights.sbomify.com/CVE-2024-4947/): Google Chromium V8 Type Confusion (critical 9.6, exploited in the wild)
- [CVE-2024-4671](https://insights.sbomify.com/CVE-2024-4671/): Google Chromium Visuals Use-After-Free (critical 9.6, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-34500 is a medium-severity cross-site scripting vulnerability in Fedoraproject Fedora, published on 5 May 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: There is no known exploitation of CVE-2024-34500 in the wild and no public exploit code.

Affected packages and fixed versions:
- samwilson/unlinked-wikibase (Packagist): affected all versions; fixed in 1.42.0
- samwilson/unlinked-wikibase (Packagist): affected all versions; fixed in 1.42.0
- mediawiki (Bitnami): affected all versions; fixed in 1.41.1

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

## Sources

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

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