dbcve.org
MediawikiCMS

CVE-2025-67477

MEDIUM · 6.1 CVSS v3.1 Published 2026-02-03
Fix available
A fix is available. Upgrade to 1.44.3 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 MediaWiki. This vulnerability is associated with program files resources/src/mediawiki.Special.Apisandbox/ApiSandboxLayout.Js. This issue affects MediaWiki: from * before 1.44.3, 1.45.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 confidence

A stored XSS vulnerability exists in MediaWiki's API Sandbox (ApiSandboxLayout.js) where user-supplied input is not properly sanitized before being rendered in web pages, allowing malicious scripts to execute in the context of other users' sessions.

MitigationUpgrade MediaWiki to version 1.44.3 or later, or 1.45.1 or later. Until then, disable the API Sandbox feature or implement content security policy headers to mitigate script execution.

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
MediawikiCMS
Affected:>= 1.44.0, < 1.44.3= 1.45.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. Identify MediaWiki version
    Check the includes/Defines.php file for the MW_VERSION constant, or access Special:Version on the wiki
    Affected if The installed version is >= 1.44.0 and < 1.44.3, or equals 1.45.0
  2. Verify API Sandbox feature is enabled
    Check if the API Sandbox module is loaded. In LocalSettings.php, look for configuration like $wgAPISandboxEnabled = true; or check if the ApiSandbox extension is loaded via $wgExtensionCredits
    Affected if The API Sandbox feature is enabled in the MediaWiki configuration
  3. Confirm API Sandbox is accessible
    Navigate to Special:ApiSandbox or access /api.php?action=edit&format=json&module=parse to see if the sandbox interface loads
    Affected if The API Sandbox interface is accessible without errors

The environment is affected if running MediaWiki version 1.44.0 through 1.44.2 or version 1.45.0 AND the API Sandbox feature is enabled and accessible.

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.44.3 or later
Fixed in 1.44.3
Interim mitigation

Upgrade MediaWiki to version 1.44.3 or later, or 1.45.1 or later. Until then, disable the API Sandbox feature or implement content security policy headers to mitigate script execution.

Recommended fix High confidence

MediaWiki 1.44.3 or 1.45.1 (depending on your branch)

  1. 1. Identify your current MediaWiki version by checking the 'includes/Defines.php' file or the Special:Version page
  2. 2. If running MediaWiki 1.44.x (1.44.0, 1.44.1, or 1.44.2), upgrade to MediaWiki 1.44.3
  3. 3. If running MediaWiki 1.45.0, upgrade to MediaWiki 1.45.1
  4. 4. Follow the standard MediaWiki upgrade process: backup database and files, upload new files, run the update.php maintenance script
  5. 5. Clear any caching systems (e.g., varnish, CDN, local cache) after upgrade
Caveat Standard MediaWiki upgrade - review release notes for any configuration or extension changes between your version and the target

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

Fix this in Mediawiki Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-67477 — 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-67477 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