# CVE-2025-61655: Stored XSS through system messages in VisualEditor

> Attackers can inject malicious scripts via system messages in VisualEditor, potentially executing code or hijacking user accounts.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Feb 2026
- **Updated:** 3 Feb 2026
- **Also known as:** DEBIAN-CVE-2025-61655, GHSA-5gh3-pm42-f6qp, UBUNTU-CVE-2025-61655

## What is CVE-2025-61655?

CVE-2025-61655 is a cross-site scripting vulnerability in Wikimedia Foundation VisualEditor, published on 3 Feb 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Wikimedia Foundation VisualEditor. This vulnerability is associated with program files includes/ApiVisualEditorEdit.Php, modules/ve-mw/init/targets/ve.Init.Mw.DesktopArticleTarget.Js, modules/ve-mw/ui/dialogs/ve.Ui.MWSaveDialog.Js.

This issue affects VisualEditor: from * before 1.39.14, 1.43.4, 1.44.1.

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

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

It affects 1 product.


Products: Mediawiki Visual Editor.

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

Upgrade to a fixed version.

## Is CVE-2025-61655 being exploited?

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

## Other vulnerabilities in Wikimedia Foundation VisualEditor

- [CVE-2019-19708](https://insights.sbomify.com/CVE-2019-19708/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2025-61656](https://insights.sbomify.com/CVE-2025-61656/): XSS when pasting into VE (not scored)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-61655 is a cross-site scripting vulnerability in Wikimedia Foundation VisualEditor, published on 3 Feb 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-61655 in the wild and no public exploit code.

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

## Sources

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

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