dbcve.org
MediawikiCMS

CVE-2026-58027

MEDIUM · 6.5 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 →
71/100
Remediation priority · Elevated
Remotely reachable 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 AbuseFilter. This vulnerability is associated with program files includes/Api/QueryAbuseFilters.Php. This issue affects AbuseFilter: 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 QueryAbuseFilters API endpoint in MediaWiki's AbuseFilter extension exposes sensitive information to unauthorized actors. This information disclosure vulnerability exists in the includes/Api/QueryAbuseFilters.php file, allowing attackers to access filter configurations, private data, or internal system details that should be restricted.

MitigationApply the vendor-supplied patches by upgrading MediaWiki to version 1.46.0, 1.45.4, 1.44.6, or 1.43.9 or later. Verify that API access controls for AbuseFilter are properly configured post-update.

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

CVSS:3.1/AV:N/AC:L/PR:L/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 installed
    Access the Special:Version page on your wiki (e.g., https://yourwiki.com/wiki/Special:Version) or run 'php maintenance/run.php version' from the command line in your MediaWiki installation directory
    Affected if The version displayed 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
  2. Verify AbuseFilter extension is enabled
    On Special:Version, confirm that 'Abuse Filter' appears in the list of installed extensions, or check your LocalSettings.php file for a line like 'wfLoadExtension( "AbuseFilter" );'
    Affected if The AbuseFilter extension is installed and enabled
  3. Confirm vulnerable API component exists
    Check if the file includes/Api/QueryAbuseFilters.php exists in your MediaWiki installation directory
    Affected if This file exists in your installation (indicating the vulnerable component is present)
  4. Check API access permissions for AbuseFilter
    Review your wiki's user rights configuration and API module permissions. Inspect whether anonymous users or unauthorized user groups can access the 'queryabusefilters' API module. Test by making an API request such as: https://yourwiki.com/api.php?action=query&list=abusefilters&format=json
    Affected if The API returns filter details or private data without requiring authentication or proper authorization checks

Your wiki is affected if it runs a MediaWiki version in the affected ranges AND has the AbuseFilter extension enabled with the QueryAbuseFilters API accessible to unauthorized users.

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

Apply the vendor-supplied patches by upgrading MediaWiki to version 1.46.0, 1.45.4, 1.44.6, or 1.43.9 or later. Verify that API access controls for AbuseFilter are properly configured post-update.

Recommended fix High confidence

Upgrade to the latest patch release in your current branch (1.43.9+, 1.44.6+, 1.45.4+, or 1.46.1+)

  1. 1. Backup your MediaWiki database and files before proceeding
  2. 2. Check your current MediaWiki version by viewing includes/Defines.php or the Special:Version page
  3. 3. For MediaWiki 1.43.x: Upgrade to version 1.43.9 or later
  4. 4. For MediaWiki 1.44.x: Upgrade to version 1.44.6 or later
  5. 5. For MediaWiki 1.45.x: Upgrade to version 1.45.4 or later
  6. 6. For MediaWiki 1.46.x: Upgrade to version 1.46.1 or later once available
  7. 7. Clear any caches (objectcaches, CDNs) after upgrade
  8. 8. Verify the upgrade by checking Special:Version shows the updated version
Caveat Minor version upgrades typically have minimal breaking changes; always review the release notes for your target version

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
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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