dbcve.org
CargoApplication · Mediawiki

CVE-2026-58521

CRITICAL · 9.8 CVSS v3.1 Published 2026-07-01
Fix available
A fix is available. Upgrade to 3.9.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available 8 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
Improper neutralization of special elements used in an SQL command ('SQL injection') vulnerability in The Wikimedia Foundation Mediawiki - Cargo Extension allows SQL Injection. This issue affects Mediawiki - Cargo Extension: from * before 1.43.9,1.44.6,1.45.4.

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

SQL injection vulnerability in the MediaWiki Cargo extension allows attackers to inject malicious SQL commands through unsanitized user input. The vulnerability affects Cargo versions before 1.43.9, 1.44.6, and 1.45.4, with a critical CVSS 9.8 score indicating remote, unauthenticated exploitation potential with full database compromise possible.

MitigationUpgrade MediaWiki Cargo extension to versions 1.43.9, 1.44.6, or 1.45.4 or later which contain the patched code. If immediate patching is not possible, temporarily disable affected Cargo functionality and implement web application firewall rules to detect and block SQL injection patterns.

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
CargoApplication
Affected:< 3.9.1

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. Check Cargo extension version
    Locate the 'extension.json' or 'Cargo.php' file in the Cargo extension directory (typically /extensions/Cargo/) and read the 'version' field from the JSON header or the $wgExtensionCredits array
    Affected if The reported version number is lower than 3.9.1
  2. Confirm Cargo extension is enabled
    Check your MediaWiki 'LocalSettings.php' file for the line 'enableExtension( 'Cargo', ... )' or 'wfLoadExtension( 'Cargo' );'
    Affected if The Cargo extension is loaded and enabled in the MediaWiki configuration
  3. Identify Cargo database tables in use
    Query your MediaWiki database for tables with the 'cargo_' prefix using: SHOW TABLES LIKE 'cargo_%';
    Affected if Cargo database tables exist, indicating the extension is actively storing or querying data
  4. Check for exposed Cargo query endpoints
    Inspect your web server logs or the MediaWiki special pages for access to Special:CargoQuery or other Cargo-related special pages that accept URL parameters
    Affected if HTTP requests to Cargo special pages with query parameters are visible in logs or the application accepts GET/POST parameters for Cargo queries

You are affected if the Cargo extension version is below 3.9.1 AND the extension is enabled with Cargo tables in use, as the SQL injection requires the vulnerable code path to be active.

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 3.9.1 or later
Fixed in 3.9.1
Vendor patch phabricator.wikimedia.org →
Interim mitigation

Upgrade MediaWiki Cargo extension to versions 1.43.9, 1.44.6, or 1.45.4 or later which contain the patched code. If immediate patching is not possible, temporarily disable affected Cargo functionality and implement web application firewall rules to detect and block SQL injection patterns.

Recommended fix High confidence

Cargo extension 3.9.1

  1. 1. Identify your current Cargo extension version by checking the 'extension.json' file in the Cargo extension directory or via Special:Version in MediaWiki
  2. 2. Confirm your MediaWiki core version (must be 1.43.9, 1.44.6, 1.45.4 or later for the fixed Cargo version)
  3. 3. Create a complete backup of your MediaWiki database before proceeding with any upgrade
  4. 4. Download Cargo extension version 3.9.1 from the MediaWiki GitHub repository or your package manager
  5. 5. Replace the existing Cargo extension files with the new version 3.9.1
  6. 6. Run the MediaWiki update script (php maintenance/update.php) to apply any database schema changes
  7. 7. Clear any caches (including objectcaches and CDNs) to ensure the new code is loaded
  8. 8. Verify the upgrade by checking Special:Version and testing Cargo functionality
Caveat Review Cargo release notes for any breaking changes between your current version and 3.9.1; test thoroughly in staging first

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

Fix this in Cargo Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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