dbcve.org
Visual EditorApplication · Mediawiki

CVE-2025-61656

MEDIUM · 6.1 CVSS v3.1 Published 2026-02-03
Fix available
A fix is available. Upgrade to 1.39.14 / 1.43.4 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
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 src/ce/ve.Ce.ClipboardHandler.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 · moderate confidence

Cross-site scripting (XSS) vulnerability in VisualEditor's clipboard handler (ve.Ce.ClipboardHandler.js) allows improper handling of clipboard input that could be rendered without proper sanitization, potentially executing malicious scripts in user browsers.

MitigationUpdate VisualEditor to version 1.39.14, 1.43.4, or 1.44.1 or later to patch the XSS vulnerability in the clipboard handler.

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
Visual EditorApplication
Affected:>= 1.39.0, < 1.39.14>= 1.43.0, < 1.43.4= 1.44.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate the VisualEditor extension directory
    Find the VisualEditor extension folder in your MediaWiki installation (typically under /extensions/VisualEditor or similar). Identify the version by checking composer.json, extension.json, or a VERSION file within that directory.
    Affected if Cannot locate the extension or version file indicates an unknown variant.
  2. Determine the installed VisualEditor version
    Read the version number from the extension's version file or package definition. Note the exact version string (for example, 1.43.0, 1.44.0, 1.39.5).
    Affected if The version cannot be determined or the extension is not installed.
  3. Compare version against affected ranges
    Check if the installed version falls into any of these ranges: 1.39.0 through 1.39.13, 1.43.0 through 1.43.3, or exactly 1.44.0. These are the vulnerable versions.
    Affected if Installed version is >= 1.39.0 and < 1.39.14, OR >= 1.43.0 and < 1.43.4, OR equals 1.44.0.
  4. Verify VisualEditor is enabled
    Check your MediaWiki configuration file (LocalSettings.php) for the line 'wfLoadExtension( 'VisualEditor' )' or similar enablement. Confirm the extension is actively loaded.
    Affected if VisualEditor is enabled and the version falls into the affected ranges.
  5. Confirm the vulnerable clipboard handler file exists
    Locate the file ve.Ce.ClipboardHandler.js within the VisualEditor extension directory structure (typically under /modules/ve-ce/). The presence of this file indicates the vulnerable component is present.
    Affected if The file exists and the extension version is in the affected ranges listed above.

Your environment is affected if VisualEditor is enabled and the installed version is any of: 1.39.0-1.39.13, 1.43.0-1.43.3, or 1.44.0.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.39.14 / 1.43.4 or later
Fixed in 1.39.141.43.4
Interim mitigation

Update VisualEditor to version 1.39.14, 1.43.4, or 1.44.1 or later to patch the XSS vulnerability in the clipboard handler.

Recommended fix High confidence

1.39.14, 1.43.4, or 1.44.1 depending on your current branch

  1. Identify the current VisualEditor version in your Wikimedia deployment
  2. For the 1.39.x branch: upgrade to version 1.39.14 or later
  3. For the 1.43.x branch: upgrade to version 1.43.4 or later
  4. For the 1.44.x branch: upgrade to version 1.44.1 or later
  5. After upgrading, verify the VisualEditor loads correctly and test clipboard functionality in the editor

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Visual Editor Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-61656 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-61656 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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