dbcve.org
MediawikiCMS

CVE-2026-58030

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 SyntaxHighlight_GeSHi. This vulnerability is associated with program files includes/SyntaxHighlight.Php. This issue affects SyntaxHighlight_GeSHi: 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 Wikimedia's SyntaxHighlight_GeSHi extension's SyntaxHighlight_Php component. User-supplied input is rendered in web pages without proper sanitization/encoding, allowing injection of malicious scripts.

MitigationUpgrade to version 1.46.0 or the patched versions (1.45.4, 1.44.6, 1.43.9) for respective release branches, or apply vendor patches to ensure proper input neutralization.

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. Check MediaWiki version
    Locate the MediaWiki version file (typically includes/Defines.php or includes/version.php) and look for the $wgVersion variable, or access /api.php?action=query&meta=siteinfo&format=json
    Affected if The installed version falls within the affected ranges: >= 1.43.0 and < 1.43.9, OR >= 1.44.0 and < 1.44.6, OR >= 1.45.0 and < 1.45.4, OR equals 1.46.0
  2. Verify SyntaxHighlight_GeSHi extension is installed
    Check the extensions/SyntaxHighlight_GeSHi directory exists in your MediaWiki installation, or check LocalSettings.php for the line: wfLoadExtension( 'SyntaxHighlight_GeSHi' )
    Affected if The SyntaxHighlight_GeSHi extension directory exists and the extension is loaded in LocalSettings.php
  3. Confirm SyntaxHighlight_Php component is in use
    Review wiki content or templates that use the <syntaxhighlight lang="php"> or <source lang="php"> tag to highlight PHP code, or check if any user-contributed pages contain PHP code blocks
    Affected if The extension is enabled and users can submit or edit content containing PHP syntax-highlighted blocks that get rendered as web output

You are affected if you run an affected MediaWiki version (1.43.0-1.43.8, 1.44.0-1.44.5, 1.45.0-1.45.3, or 1.46.0) with the SyntaxHighlight_GeSHi extension installed and users can create or edit content containing PHP code blocks.

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 version 1.46.0 or the patched versions (1.45.4, 1.44.6, 1.43.9) for respective release branches, or apply vendor patches to ensure proper input neutralization.

Recommended fix High confidence

MediaWiki 1.46.1 or later (alternatively: 1.45.4+, 1.44.6+, or 1.43.9+)

  1. 1. Back up your MediaWiki installation and database before proceeding with the upgrade.
  2. 2. Identify your current MediaWiki version by checking the includes/Defines.php file or the Special:Version page.
  3. 3. Download the appropriate fixed release: upgrade to 1.46.1 (or later), 1.45.4 (or later), 1.44.6 (or later), or 1.43.9 (or later) depending on your current branch.
  4. 4. Replace the existing MediaWiki files with the new version files, preserving your LocalSettings.php configuration.
  5. 5. Run the MediaWiki update script (php maintenance/update.php) if required for database schema updates.
  6. 6. Verify the upgrade was successful by checking Special:Version and testing the SyntaxHighlight functionality.
Caveat Review the MediaWiki release notes for your target version to check for any breaking changes or configuration changes required.

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

Fix this in Mediawiki Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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