dbcve.org
MediawikiCMS

CVE-2026-58024

MEDIUM · 5.7 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 →
61/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
Exposure of Sensitive Information to an Unauthorized Actor vulnerability in Wikimedia Foundation MediaWiki. This vulnerability is associated with program files includes/Api/ApiUserrights.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 · moderate confidence

The ApiUserrights.php API module in MediaWiki exposes sensitive information to unauthorized actors. This module handles user rights queries, and the vulnerability allows attackers to potentially access information about user permissions and group memberships that should be restricted.

MitigationUpgrade MediaWiki to version 1.46.0, 1.45.4, 1.44.6, or 1.43.9 or later to patch this information disclosure vulnerability.

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
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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. Identify MediaWiki installation path
    Locate the MediaWiki installation directory on your server. Common paths include /var/www/html/, /home/user/public_html/, or check your web server configuration.
    Affected if MediaWiki is not installed on the system
  2. Determine installed MediaWiki version
    Check the includes/Defines.php file or the Special:Version page (accessed via web browser). Look for the $wgVersion variable or the version number displayed.
    Affected if The installed version is >= 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
  3. Verify ApiUserrights API module exists
    Check for the presence of the ApiUserrights.php file in the includes/api/ or api/ directory of your MediaWiki installation.
    Affected if The file exists in the installation
  4. Confirm API is externally accessible
    Test access to the API endpoint by making a request to /api.php?action=query&list=users&format=json or similar API endpoint from an unauthorized network location.
    Affected if The API is reachable from the network without authentication
  5. Check API user rights query behavior
    Send a crafted request to the ApiUsermights module as an anonymous or unauthorized user: /api.php?action=query&list=users&usprop=rights&format=json
    Affected if The API returns user rights or group membership information without proper authorization checks

If your MediaWiki version falls within the affected ranges (1.43.0-1.43.8, 1.44.0-1.44.5, 1.45.0-1.45.3, or 1.46.0) and the API module is accessible, your installation is vulnerable to unauthorized access of user permission information.

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 MediaWiki to version 1.46.0, 1.45.4, 1.44.6, or 1.43.9 or later to patch this information disclosure vulnerability.

Recommended fix High confidence

Upgrade to 1.43.9 (for 1.43.x), 1.44.6 (for 1.44.x), 1.45.4 (for 1.45.x), or 1.46.1+ (for 1.46.x)

  1. 1. Identify your current MediaWiki version by checking the includes/Defines.php file or the Special:Version page
  2. 2. Determine which version branch you are on (1.43.x, 1.44.x, 1.45.x, or 1.46.x)
  3. 3. Plan upgrade to the appropriate fixed version for your branch
  4. 4. Create a full backup of your MediaWiki database and all files
  5. 5. Test the upgrade in a staging environment before applying to production
  6. 6. Follow the official MediaWiki upgrade guide to upgrade to the fixed version
  7. 7. Clear all MediaWiki caches after upgrade (php maintenance/run.php invalidateCache)
  8. 8. Verify the ApiUserrights.php file has been updated and the vulnerability is resolved
Caveat Minor version upgrades typically have minimal breaking changes; review the release notes for your target version for any migration notes or deprecation warnings

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
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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