# CVE-2025-67479: Magic word replacement in legacy parser allows using reserved data attributes through wikitext

> Attackers can inject malicious scripts via reserved data attributes in wikitext, potentially executing code or bypassing security controls in MediaWiki.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Feb 2026
- **Updated:** 2 Mar 2026
- **Also known as:** DEBIAN-CVE-2025-67479, GHSA-mvgm-9fcq-x877, UBUNTU-CVE-2025-67479

## What is CVE-2025-67479?

CVE-2025-67479 is a cross-site scripting vulnerability in Wikimedia Foundation Cite, published on 3 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vulnerability in Wikimedia Foundation MediaWiki, Wikimedia Foundation Cite. This vulnerability is associated with program files includes/Parser/CoreParserFunctions.Php, includes/Parser/Sanitizer.Php.

This issue affects MediaWiki: from * before 1.39.14, 1.43.4, 1.44.1; Cite: from * before 1.39.14, 1.43.4, 1.44.1.

## Which versions are affected by CVE-2025-67479?


## How do I fix CVE-2025-67479?

Upgrade to a fixed version.

## Is CVE-2025-67479 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-67479 and fix it if it is affected.

What it is: CVE-2025-67479 is a cross-site scripting vulnerability in Wikimedia Foundation Cite, published on 3 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-67479 in the wild and no public exploit code.

Affected product: Wikimedia Foundation Cite. 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-2025-67479/ (Markdown: https://insights.sbomify.com/CVE-2025-67479/index.md)
```

## Sources

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

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