dbcve.org
MediawikiCMS

CVE-2026-58033

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 →
72/100
Remediation priority · Elevated
Remotely reachable No privileges 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/Actions/InfoAction.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

An information disclosure vulnerability exists in MediaWiki's includes/Actions/InfoAction.php file, allowing unauthorized actors to access sensitive information. The vulnerability affects MediaWiki versions prior to 1.46.0, 1.45.4, 1.44.6, and 1.43.9.

MitigationUpgrade MediaWiki to version 1.46.0 or later, or apply the specific patches for versions 1.45.4, 1.44.6, or 1.43.9 to remediate the sensitive information exposure in InfoAction.php.

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Determine installed MediaWiki version
    Check the includes/Defines.php file for the MW_VERSION constant, or access Special:Version page on the wiki, or run 'php maintenance/run.php version' if maintenance scripts are available
    Affected if The version is 1.43.0 through 1.43.8, 1.44.0 through 1.45.3, or exactly 1.46.0
  2. Verify InfoAction.php file exists
    Locate the includes/Actions/InfoAction.php file in the MediaWiki installation directory and verify it is present
    Affected if The file exists and the version check shows an affected version
  3. Test InfoAction endpoint accessibility
    Access the URL pattern 'https://yourwiki.com/index.php?title=Special:Version&action=info' or append '&action=info' to any wiki page URL to invoke the InfoAction
    Affected if The endpoint responds and returns page information (the vulnerability allows unauthorized access to sensitive information through this action)
  4. Check for sensitive information exposure
    Compare the output from the action=info endpoint against expected behavior - the vulnerability allows access to potentially sensitive configuration or metadata that should require higher privileges
    Affected if The info action returns sensitive data that should not be accessible to unauthorized users, or returns data that differs from expected public information

If MediaWiki version is 1.43.0-1.43.8, 1.44.0-1.45.3, or exactly 1.46.0 AND the InfoAction.php file is present and accessible, the environment is likely affected by this information disclosure vulnerability.

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 or later, or apply the specific patches for versions 1.45.4, 1.44.6, or 1.43.9 to remediate the sensitive information exposure in InfoAction.php.

Recommended fix High confidence

Upgrade to 1.43.9, 1.44.6, 1.45.4, or 1.46.1 (whichever is the minimum for your major version branch)

  1. 1. Backup your MediaWiki database and all files before making any changes
  2. 2. Determine your current MediaWiki version by checking LocalSettings.php or the Special:Version page
  3. 3. Download the appropriate fixed version from https://www.mediawiki.org/wiki/Download (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.0)
  4. 4. Extract the new version and replace your existing MediaWiki files, or at minimum replace includes/Actions/InfoAction.php with the version from the fixed release
  5. 5. Run the update.php maintenance script if doing a partial file replacement
  6. 6. Clear any caching systems (e.g., Redis, Memcached) and PHP OPcache
  7. 7. Verify the fix by accessing Special:Info and confirming no sensitive information is exposed
Caveat Standard MediaWiki upgrade precautions apply; test in staging first, review extension compatibility

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mediawiki Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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