dbcve.org
MediawikiCMS

CVE-2026-14358

MEDIUM · 6.1 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 →
68/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
Improper neutralization of input during web page generation ('cross-site scripting') vulnerability in The Wikimedia Foundation Mediawiki - Charts Extension allows Cross-Site Scripting (XSS). This issue affects Mediawiki - Charts 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 · moderate confidence

Cross-site scripting (XSS) vulnerability in the Mediawiki Charts Extension allows attackers to inject malicious scripts into web pages through improper input neutralization. The vulnerability stems from the Charts Extension failing to properly sanitize user-supplied data before rendering it in generated charts or chart-related output.

MitigationUpgrade the Mediawiki Charts Extension to version 1.43.9, 1.44.6, 1.45.4 or later to remediate the XSS vulnerability. Alternatively, disable the Charts Extension until a patch can be applied.

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

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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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. Check MediaWiki core version
    Navigate to Special:Version on your wiki or query the API via ?action=query&meta=siteinfo&format=json to retrieve the software version
    Affected if The installed version is >= 1.43.0 and < 1.43.9, OR >= 1.44.0 and < 1.44.6, OR >= 1.45.0 and < 1.45.4
  2. Verify Charts Extension is installed
    Check the Special:Version page for an entry titled 'Charts' or 'Extension:Charts'. Alternatively, look for the extension in the 'extensions/Charts' or 'extensions/WikibaseCharts' directory of your MediaWiki installation
    Affected if The Charts Extension appears in the list of installed extensions
  3. Confirm Charts Extension is enabled
    Check your LocalSettings.php for a line such as 'wfLoadExtension( 'Charts' );' or 'enableSemantics'; also check if the extension directory contains an extension.json or composer.json file indicating it is loaded
    Affected if The extension is loaded and active in your MediaWiki configuration
  4. Determine Charts Extension version if available
    On Special:Version, look for the version number listed next to the Charts Extension entry. Some versions display it alongside the extension name
    Affected if The Charts Extension version, if displayed, falls within the same vulnerable ranges as the core (prior to 1.43.9, 1.44.6, or 1.45.4)

You are affected if your MediaWiki version falls within the vulnerable ranges AND the Charts Extension is installed and enabled, allowing user-supplied data to be rendered in charts without sanitization.

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 the Mediawiki Charts Extension to version 1.43.9, 1.44.6, 1.45.4 or later to remediate the XSS vulnerability. Alternatively, disable the Charts Extension until a patch can be applied.

Recommended fix High confidence

Upgrade Mediawiki Charts Extension to 1.43.9 (for MW 1.43.x), 1.44.6 (for MW 1.44.x), or 1.45.4 (for MW 1.45.x)

  1. 1. Identify your current Mediawiki Charts Extension version by checking the extension's version file or Composer vendor directory.
  2. 2. For Mediawiki 1.43.x: Upgrade the Charts Extension to version 1.43.9 or later.
  3. 3. For Mediawiki 1.44.x: Upgrade the Charts Extension to version 1.44.6 or later.
  4. 4. For Mediawiki 1.45.x: Upgrade the Charts Extension to version 1.45.4 or later.
  5. 5. Run the Mediawiki update script (update.php) if required by the extension upgrade.
  6. 6. Clear any caches (objectcaches, cdbs) to ensure the new extension code is loaded.
  7. 7. Verify the upgrade was successful by checking the Special:Version page in your Mediawiki installation.
Caveat Review the Wikimedia release notes for any breaking changes between your current version and the target version

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

Fix this in Mediawiki Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
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,072.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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