dbcve.org
CargoApplication · Mediawiki

CVE-2026-58519

MEDIUM · 5.4 CVSS v3.1 Published 2026-07-01
Fix available
A fix is available. Upgrade to 3.9.1 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable 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
Improper neutralization of input during web page generation ('cross-site scripting') vulnerability in The Wikimedia Foundation Mediawiki - Cargo Extension allows Stored XSS. This issue affects Mediawiki - Cargo Extension: from * before 3.9.1.

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

A Stored XSS vulnerability exists in the MediaWiki Cargo Extension where user-supplied input is not properly sanitized before being rendered in web pages. This allows authenticated attackers to inject malicious JavaScript that executes in the browsers of other users who view the affected content.

MitigationUpgrade the MediaWiki Cargo Extension to version 3.9.1 or later which contains the patch for this vulnerability.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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. Verify Cargo extension is installed
    Check your MediaWiki installation for the Cargo extension by looking for the Cargo directory in the extensions folder, or check LocalSettings.php for 'wfLoadExtension( Cargo )' or similar Cargo-related configuration
    Affected if The Cargo extension is present in the MediaWiki installation
  2. Determine installed Cargo extension version
    Open the Cargo extension's composer.json, VERSION file, or the main PHP file (e.g., Cargo.php) in the extension directory and look for the version number
    Affected if The version number found is less than 3.9.1
  3. Check MediaWiki version for context
    Check MediaWiki's Special:Version page or the includes/Defines.php file to confirm the MediaWiki version in use
    Affected if Running any supported MediaWiki version with a vulnerable Cargo version (< 3.9.1)
  4. Confirm Cargo database tables exist
    Look for Cargo-related database tables in your MediaWiki database (typically prefixed with 'cargo_') - these indicate Cargo is actively in use
    Affected if Cargo database tables exist and the Cargo extension version is below 3.9.1

Your environment is affected if the Cargo extension is installed and its version is lower than 3.9.1, regardless of whether user-generated content with Cargo fields is currently present.

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
Interim mitigation

Upgrade the MediaWiki Cargo Extension to version 3.9.1 or later which contains the patch for this vulnerability.

Recommended fix Moderate confidence

Cargo extension version 3.9.1

  1. 1. Backup your current MediaWiki installation and database before performing any upgrade.
  2. 2. Locate the Cargo extension in your MediaWiki extensions directory (usually /path/to/mediawiki/extensions/Cargo).
  3. 3. Update the Cargo extension to version 3.9.1 or later. The method depends on your installation:
  4. - If using Git: Run 'git fetch' and 'git checkout REL1_39' (or appropriate branch) followed by 'git pull' to get the latest version.
  5. - If using Composer: Run 'composer update wikimedia/cargo' or download the new version manually.
  6. 4. Clear any cached data: Delete the contents of the 'cache' directory in your MediaWiki installation.
  7. 5. Run the MediaWiki update script: 'php maintenance/update.php' from your MediaWiki root directory.
  8. 6. Verify the upgrade was successful by checking the Special:Version page in your wiki to confirm Cargo version 3.9.1 or later is installed.
Caveat Review the Cargo extension release notes for version 3.9.1 to check for any breaking changes or database schema updates that may affect your existing Cargo tables.

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

Fix this in Cargo Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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