dbcve.org
MediawikiCMS

CVE-2026-58031

MEDIUM · 5.4 CVSS v3.1 Published 2026-07-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable 7 weeks old

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 1.46.0-rc.0 before 1.46.0.

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

An XSS vulnerability exists in MediaWiki's API Sandbox layout JavaScript (ApiSandboxLayout.js) where user-controlled input is not properly neutralized before being rendered in web pages. This allows attackers to inject malicious scripts that execute in the context of other users' browsers.

MitigationUpgrade MediaWiki to version 1.46.0 or later. For immediate mitigation, disable or restrict access to the API Sandbox feature until the patch can be applied.

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.46.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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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. Check MediaWiki version
    Visit Special:Version on your wiki, or inspect includes/Defines.php for the MW_VERSION constant, or check your LocalSettings.php for the version number
    Affected if The installed version is 1.46.0 (the specific version noted in affected products)
  2. Verify API Sandbox feature is enabled
    Check if the API Sandbox module is accessible by navigating to api.php?action=apierror&format=json&errorformat=html&code=readapidenied (or check Special:ApiSandbox if the feature has a user interface)
    Affected if The API Sandbox is accessible to users who can craft API requests
  3. Confirm API Sandbox is in use
    Review your wiki's API documentation or check if users have access to the API Sandbox tool for testing MediaWiki API queries
    Affected if Users can access and use the API Sandbox interface to make API requests

Your environment is affected if you are running MediaWiki version 1.46.0 with the API Sandbox feature enabled and accessible to users.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade MediaWiki to version 1.46.0 or later. For immediate mitigation, disable or restrict access to the API Sandbox feature until the patch can be applied.

Recommended fix High confidence

1.46.0

  1. 1. Back up your MediaWiki installation and database before proceeding.
  2. 2. Download MediaWiki version 1.46.0 from the official MediaWiki release page (https://www.mediawiki.org).
  3. 3. Replace the existing MediaWiki files with the new version 1.46.0 files, preserving your LocalSettings.php configuration.
  4. 4. Run the MediaWiki update script (php maintenance/update.php) if required for database schema changes.
  5. 5. Clear any caching systems (e.g., Redis, Memcached) and web server caches.
  6. 6. Verify the Special:ApiSandbox page functions correctly and that the XSS vulnerability is resolved.
Caveat Review the MediaWiki 1.46.0 release notes for any breaking changes or deprecated features before upgrading

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 help mitigating

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-2026-58031 — 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-2026-58031 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