dbcve.org
MediawikiCMS

CVE-2026-34092

HIGH · 7.5 CVSS v3.1 Published 2026-05-11
Fix available
A fix is available. Upgrade to 1.43.7 / 1.44.4 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
Exposure of Sensitive Information to an Unauthorized Actor vulnerability in Wikimedia Foundation MediaWiki. This vulnerability is associated with program files includes/Skin/Skin.Php. This issue affects MediaWiki: from * before 1.43.7, 1.44.4, 1.45.2.

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

An information disclosure vulnerability exists in MediaWiki's Skin component (includes/Skin/Skin.php) that allows unauthorized actors to access sensitive information. The vulnerability is present in versions prior to 1.43.7, 1.44.4, and 1.45.2.

MitigationUpgrade MediaWiki to version 1.43.7, 1.44.4, or 1.45.2 or later to apply the security patch.

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.7>= 1.44.0, < 1.44.4>= 1.45.0, < 1.45.2

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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 via command line
    Run `php maintenance/showMWVersion.php` from the MediaWiki installation directory, or check the VERSION file in the root directory
    Affected if The version is less than 1.43.7, OR between 1.44.0 and 1.44.4 (exclusive), OR between 1.45.0 and 1.45.2 (exclusive)
  2. Check MediaWiki version via web interface
    Navigate to Special:Version on your wiki (e.g., yourwiki.com/wiki/Special:Version)
    Affected if The displayed MediaWiki version falls within the vulnerable ranges specified above
  3. Identify the Skin component file
    Locate the file includes/Skin/Skin.php in your MediaWiki installation directory
    Affected if The file exists and your MediaWiki version is vulnerable according to version checks above
  4. Verify Skin module is active
    Check your LocalSettings.php for custom skin configurations or visit Special:Preferences to see enabled skins
    Affected if Any skin is enabled and your version is in the affected range (the vulnerability resides in the core Skin class)
  5. Review web server access logs
    Examine access logs for unusual requests to skin-related endpoints that may indicate exploitation attempts
    Affected if Suspicious patterns found and version is confirmed vulnerable

A MediaWiki installation is affected if it runs version 1.43.x below 1.43.7, 1.44.x below 1.44.4, or 1.45.x below 1.45.2 and has any skin enabled.

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.7 / 1.44.4 / 1.45.2 or later
Fixed in 1.43.71.44.41.45.2
Interim mitigation

Upgrade MediaWiki to version 1.43.7, 1.44.4, or 1.45.2 or later to apply the security patch.

Recommended fix High confidence

Upgrade to MediaWiki 1.43.7, 1.44.4, or 1.45.2 (depending on your release branch)

  1. 1. Back up your MediaWiki database and files before upgrading.
  2. 2. Download MediaWiki version 1.43.7, 1.44.4, or 1.45.2 (whichever is appropriate for your branch) from https://www.mediawiki.org/wiki/Download.
  3. 3. Extract the new version to a temporary location.
  4. 4. Replace the existing includes/Skin/Skin.php file with the new version, or replace the entire installation.
  5. 5. Run the update.php maintenance script: php maintenance/update.php
  6. 6. Clear any caching systems (e.g., Memcached, Redis) and CDNs.
  7. 7. Verify the installation by accessing MediaWiki and checking Special:Version.
Caveat Review the release notes for your target version for any configuration or extension compatibility changes 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
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
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,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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