dbcve.org
MediawikiCMS

CVE-2026-34093

MEDIUM · 5.3 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 →
62/100
Remediation priority · Elevated
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/Specials/SpecialUserRights.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

The SpecialUserRights.php component in MediaWiki contains an information disclosure vulnerability that allows unauthorized access to sensitive user rights data. This could expose user group assignments, permission levels, or administrative configuration details to actors who should not have access to this information.

MitigationUpgrade MediaWiki to version 1.43.7, 1.44.4, or 1.45.2 or later to obtain the patched code. Review user access controls and audit user rights assignments after patching.

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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. Identify installed MediaWiki version
    Check the version file in your MediaWiki installation. The version is typically stored in includes/Defines.php or can be retrieved by accessing the Special:Version page on the wiki.
    Affected if The installed version is less than 1.43.7, or between 1.44.0 and 1.44.4, or between 1.45.0 and 1.45.2.
  2. Locate SpecialUserRights.php component
    Verify the presence of SpecialUserRights.php in the includes/specials directory of your MediaWiki installation.
    Affected if The file exists and the installed MediaWiki version falls within the affected version ranges.
  3. Verify access control on Special:UserRights
    Test whether unauthorized or low-privilege users can access the Special:UserRights page. Attempt to access it with a non-administrator account or inspect the $wgGroupPermissions configuration in LocalSettings.php.
    Affected if Users without proper rights (such as anonymous users or regular users) can access Special:UserRights and view user rights data.
  4. Check for exposed user rights information
    If Special:UserRights is accessible, examine whether it exposes user group assignments, permission levels, or administrative configuration to unauthorized users by visiting the page.
    Affected if Sensitive user rights data is visible to actors who should not have access to this information.

You are affected if your MediaWiki version is within the vulnerable ranges AND unauthorized users can access the Special:UserRights page to view sensitive user rights data.

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 obtain the patched code. Review user access controls and audit user rights assignments after patching.

Recommended fix Moderate confidence

1.43.7 (for 1.43.x), 1.44.4 (for 1.44.x), or 1.45.2 (for 1.45.x)

  1. 1. Identify current MediaWiki version by checking includes/Defines.php or the special version page
  2. 2. Determine which version branch you are on (1.43.x, 1.44.x, or 1.45.x)
  3. 3. Backup the MediaWiki database and all files
  4. 4. Download the appropriate fixed version: 1.43.7 for 1.43.x, 1.44.4 for 1.44.x, or 1.45.2 for 1.45.x
  5. 5. Replace MediaWiki core files with the new version files
  6. 6. Run the update.php maintenance script via CLI: php maintenance/update.php
  7. 7. Clear all caches (including any opcode caches)
  8. 8. Verify the upgrade was successful by checking the MediaWiki version
Caveat Review the release notes for the target version to check for any breaking changes or required configuration updates

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
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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