dbcve.org
MediawikiCMS

CVE-2026-58025

CRITICAL · 9.8 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 →
100/100
Remediation priority · Urgent
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
Deserialization of untrusted data vulnerability in Wikimedia Foundation MediaWiki. This vulnerability is associated with program files includes/Import/WikiImporter.Php, includes/Import/WikiRevision.Php, includes/Logging/LogEntryBase.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 · high confidence

A deserialization of untrusted data vulnerability exists in MediaWiki's import and logging modules (WikiImporter.php, WikiRevision.php, LogEntryBase.php). The vulnerability allows remote attackers to execute arbitrary code by supplying malicious serialized PHP objects through the affected import/logging functions.

MitigationUpgrade MediaWiki to version 1.46.0, 1.45.4, 1.44.6, or 1.43.9 or later. If immediate upgrade is not possible, disable or restrict the XML import functionality and review logging configurations to prevent untrusted data deserialization.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 version
    Check the installed MediaWiki version by examining the includes/Defines.php file, or access Special:Version on the wiki, or run 'grep wgVersion includes/Defines.php'
    Affected if The version falls within these ranges: 1.43.0 to 1.43.8, 1.44.0 to 1.44.5, 1.45.0 to 1.45.3, or exactly 1.46.0
  2. Verify XML import is enabled
    Check LocalSettings.php for the $wgImportSources variable or verify if Special:Import page is accessible. Also check if $wgEnableImport is set to true
    Affected if XML import functionality is enabled and accessible to users who can supply untrusted import content
  3. Check logging module configuration
    Examine LocalSettings.php for $wgLogSettings and review the logging configuration in includes/LogEntryBase.php to see if untrusted data can be passed to log functions
    Affected if Logging accepts untrusted serialized data through log entry processing
  4. Confirm WikiImporter module is active
    Look for the presence of includes/import/WikiImporter.php and check if the import feature is configured in the wiki's user permissions (import special page)
    Affected if WikiImporter.php is present and import permissions allow untrusted users to trigger import operations

The environment is affected if MediaWiki version is in the vulnerable range AND the XML import or logging features are accessible to untrusted users who can supply serialized 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.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. If immediate upgrade is not possible, disable or restrict the XML import functionality and review logging configurations to prevent untrusted data deserialization.

Recommended fix High confidence

1.43.9, 1.44.6, 1.45.4, or 1.46.1 (depending on your branch)

  1. 1. Backup your MediaWiki database and files before proceeding with any upgrade.
  2. 2. Review the MediaWiki upgrade guide at https://www.mediawiki.org/wiki/Manual:Upgrading for your current version.
  3. 3. Download the appropriate fixed version (1.43.9, 1.44.6, 1.45.4, or 1.46.1) from https://www.mediawiki.org/wiki/Download.
  4. 4. Replace your existing MediaWiki installation files with the new version, preserving your LocalSettings.php configuration.
  5. 5. Run the maintenance/update.php script: php maintenance/update.php
  6. 6. Verify the installation by accessing your wiki and checking Special:Version to confirm the new version is running.
  7. 7. Test critical functionality including import features since the vulnerability is in WikiImporter.php and WikiRevision.php.
Caveat Review MediaWiki release notes for your target version for any configuration or extension changes that may require attention

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-58025 — 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-58025 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