dbcve.org
MediawikiCMS

CVE-2026-58036

HIGH · 7.5 CVSS v3.1 Published 2026-07-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click 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/ApiQueryAllUsers.Php, includes/Api/ApiQueryUsers.Php, includes/Permissions/PermissionManager.Php, includes/User/UserGroupManager.Php.

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

This is an information disclosure vulnerability in MediaWiki's user query APIs (ApiQueryAllUsers and ApiQueryUsers) combined with PermissionManager and UserGroupManager components. The vulnerability allows unauthorized actors to access sensitive user information such as group memberships, permissions, or other user-specific data that should be restricted.

MitigationApply the vendor patch for CVE-2026-58036 which adds proper authorization checks in the affected API query and user management files to prevent unauthorized access to sensitive user data.

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.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
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
    Locate the MediaWiki installation directory and find the VERSION file (usually in the root directory) or check the 'wgVersion' variable in LocalSettings.php. Alternatively, query the API endpoint at /api.php?action=query&meta=siteinfo&format=json and look for the 'version' field in the response.
    Affected if The installed version is exactly 1.46.0 (the affected version).
  2. Verify API access is enabled
    Confirm that api.php is accessible on the server (typically at /api.php in the MediaWiki root). Check LocalSettings.php for any disabled API modules via $wgAPIModules or $wgDisableAPI.
    Affected if The API is enabled and accessible to the network or users in scope.
  3. Test ApiQueryUsers module accessibility
    Send a request to api.php with parameters: action=query&list=users&usprop=groups|rights|blockinfo&format=json. Observe if the response returns user group memberships, rights, or block information without requiring elevated permissions.
    Affected if The API returns sensitive user data (groups, rights, block status) to an unauthorized or low-privileged user.
  4. Test ApiQueryAllUsers module accessibility
    Send a request to api.php with parameters: action=query&list=allusers&auprop=groups|rights&format=json. Observe if the response exposes group memberships or permissions for users.
    Affected if The API returns group memberships or permission data without proper authorization checks.
  5. Check user permission configuration
    Review LocalSettings.php for $wgGroupPermissions settings. Specifically check if anonymous users or low-privilege accounts have 'queryuser' or 'queryallusers' rights granted via $wgGroupPermissions.
    Affected if Anonymous or user accounts have been granted API query permissions that should be restricted.

A user is affected if running MediaWiki version 1.46.0 AND the API is accessible with permissions that allow unauthenticated or low-privileged users to query user information via ApiQueryAllUsers or ApiQueryUsers modules.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor patch for CVE-2026-58036 which adds proper authorization checks in the affected API query and user management files to prevent unauthorized access to sensitive user data.

Fix this in Mediawiki Scoped from the published advisory
  • Consultation3.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
24.0 hours of engineering $4,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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