CVE-2025-61655
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedImproper 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceCross-site scripting (XSS) vulnerability in Wikimedia VisualEditor's save dialog and desktop article target components. User-supplied input in the save dialog (ve.Ui.MWSaveDialog.js) or desktop article target (ve.Init.Mw.DesktopArticleTarget.js) is not properly sanitized before being rendered in web pages, allowing injection of malicious scripts.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 1.39.0, < 1.39.14>= 1.43.0, < 1.43.4= 1.44.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify VisualEditor versionNavigate to Special:Version on your MediaWiki installation or check the extensions/VisualEditor/extension.json file to determine the installed versionAffected if Installed version is >= 1.39.0 and < 1.39.14, OR >= 1.43.0 and < 1.43.4, OR exactly 1.44.0
-
Verify VisualEditor is enabledCheck LocalSettings.php for lines containing wfLoadExtension('VisualEditor') or require_once to confirm the extension is loadedAffected if VisualEditor extension is loaded and accessible to users
-
Check save dialog componentLocate the ve.Ui.MWSaveDialog.js file in the VisualEditor extension directory and inspect code that handles user input before renderingAffected if The file contains user-supplied input that is not sanitized before being output
-
Check desktop article target componentLocate the ve.Init.Mw.DesktopArticleTarget.js file in the VisualEditor extension directory and inspect code that handles user input before renderingAffected if The file contains user-supplied input that is not sanitized before being output
Your environment is affected if VisualEditor is enabled and your installed version falls within the vulnerable ranges (>=1.39.0,<1.39.14 OR >=1.43.0,<1.43.4 OR =1.44.0)
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.39.141.43.4
Update VisualEditor to version 1.39.14, 1.43.4, 1.44.1 or later to include the XSS patch. Until then, restrict access to VisualEditor editing features or implement WAF rules to filter script injection attempts in relevant parameters.
VisualEditor 1.39.14, 1.43.4, or 1.44.1 (choose based on your release line)
- 1. Identify the currently installed VisualEditor extension version in your MediaWiki installation
- 2. Determine which upgrade path applies based on your current version (1.39.x, 1.43.x, or 1.44.0)
- 3. Backup your MediaWiki database and files before proceeding
- 4. Update the VisualEditor extension to the appropriate fixed version using your MediaWiki package manager or by downloading the new version from Wikimedia's extension repository
- 5. Clear any caches (including the MediaWiki cache and any CDN caches)
- 6. Verify the new version is correctly installed by checking the Special:Version page in your MediaWiki wiki
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-61655 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-61655 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data