dbcve.org
MediawikiCMS

CVE-2026-58037

MEDIUM · 6.1 CVSS v3.1 Published 2026-07-01
Fix available
A fix is available. Upgrade to 1.43.9 / 1.44.6 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges 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 includes/Language/Language.Php, includes/Logging/BlockLogFormatter.Php, includes/Logging/LogFormatter.Php, includes/Logging/PatrolLogFormatter.Php, includes/Logging/RenameuserLogFormatter.Php, includes/Logging/TagLogFormatter.Php, includes/Specials/SpecialVersion.Php. This issue affects MediaWiki: from * before 1.46.0, 1.45.4, 1.44.6, 1.43.9.

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

Cross-site scripting (XSS) vulnerability in MediaWiki's logging formatters (BlockLogFormatter, PatrolLogFormatter, RenameuserLogFormatter, TagLogFormatter, LogFormatter), language handling (Language.php), and Special:Version page. User-supplied input in log entries or user-generated content is rendered without proper output encoding, allowing injection of malicious HTML/JavaScript.

MitigationUpgrade to MediaWiki 1.46.0, 1.45.4, 1.44.6, or 1.43.9 (or later patched versions). Alternatively, apply output encoding/escaping to user inputs in the affected files before rendering.

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.43.0, < 1.43.9>= 1.44.0, < 1.44.6>= 1.45.0, < 1.45.4= 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
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
    Run the command: php maintenance/run.php eval 'echo wfVersion();' or access Special:Version in the web browser to view the installed version number.
    Affected if The installed version falls within one of these ranges: >= 1.43.0 and < 1.43.9, >= 1.44.0 and < 1.44.6, >= 1.45.0 and < 1.45.4, or equals 1.46.0
  2. Check if log entries are being viewed
    Access Special:Log in the web browser and view log entries, particularly block logs, patrol logs, renameuser logs, or tag logs.
    Affected if Log entries containing user-supplied input (usernames, block reasons, tag names) are displayed without visible encoding, indicating the vulnerable log formatters are in use
  3. Verify Special:Version page accessibility
    Access Special:Version in the web browser as any user, including anonymous users.
    Affected if The Special:Version page is accessible and displays information that could be manipulated through user-generated content
  4. Identify log formatter usage in custom code
    Search PHP source files for usages of the affected LogFormatter subclasses: BlockLogFormatter, PatrolLogFormatter, RenameuserLogFormatter, TagLogFormatter, or the base LogFormatter class.
    Affected if Custom extensions or skins are using any of these log formatter classes to process user-controlled log data

A user is affected if their MediaWiki installation version matches any of the affected ranges AND either log entries are displayed to users or Special:Version is accessible, as these are the vectors for the XSS injection.

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.43.9 / 1.44.6 / 1.45.4 or later
Fixed in 1.43.91.44.61.45.4
Interim mitigation

Upgrade to MediaWiki 1.46.0, 1.45.4, 1.44.6, or 1.43.9 (or later patched versions). Alternatively, apply output encoding/escaping to user inputs in the affected files before rendering.

Recommended fix High confidence

1.46.1 (or latest stable 1.46.x release)

  1. 1. Back up your MediaWiki database and file system before proceeding
  2. 2. Identify your current MediaWiki version by checking includes/DefaultSettings.php or the Special:Version page
  3. 3. For MediaWiki 1.43.x: Upgrade to version 1.43.9 or later
  4. 4. For MediaWiki 1.44.x: Upgrade to version 1.44.6 or later
  5. 5. For MediaWiki 1.45.x: Upgrade to version 1.45.4 or later
  6. 6. For MediaWiki 1.46.0: Upgrade to version 1.46.1 or later
  7. 7. After upgrading, clear any caches and verify the installation at Special:Version
  8. 8. Test that log pages (Special:Log) and Special:Version render correctly to confirm the XSS fix is applied
Caveat Review MediaWiki release notes for your upgrade path - minor version upgrades typically have low breaking change risk but always test in staging first

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

Fix this in Mediawiki Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,480
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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