Loading vulnerability…
CVE-2026-58025 is a deserialization of untrusted data vulnerability in Wikimedia Foundation MediaWiki. The issue is associated with MediaWiki import and logging code, including WikiImporter, WikiRevision, and LogEntryBase, with available context specifically referencing LogEntryBase::extractParams(). Unsafe handling of serialized attacker-controlled data can cause the application to reconstruct unexpected objects or data structures during processing, creating a path to application compromise. In affected deployments, this can expose a route to remote code execution depending on the reachable deserialization path and the availability of exploitable gadget chains in the application environment. Affected versions are MediaWiki releases before 1.46.0, before 1.45.4, before 1.44.6, and before 1.43.9.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository is a small standalone Python proof-of-concept exploit for CVE-2026-58025, a MediaWiki PHP deserialization vulnerability reachable through log entry import. The repo contains one executable code file (exploit.py), a detailed README, and standard metadata files (.gitignore, LICENSE). The Python script is the clear entry point and implements three main capabilities: (1) generate a MediaWiki XML import payload containing attacker-controlled serialized PHP data in a <params> field, (2) fingerprint a target MediaWiki instance and infer likely vulnerability from the exposed generator version, and (3) attempt authenticated import of the malicious XML into the target. The exploit abuses the Special:Import workflow and relies on a user with import/importupload privileges. Included payloads are mostly demonstrative: a safe serialized array, a stdClass probe to show unsafe object handling, and a placeholder gadget payload rather than a real target-specific POP chain. As such, the code is operational but not fully weaponized; it automates delivery and validation, but successful RCE still depends on identifying a usable gadget chain in the target’s installed PHP classes. The repository purpose is to demonstrate and automate exploitation workflow for MediaWiki log-parameter deserialization via XML import, not merely detect the issue.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
12 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.