dbcve.org
MediawikiCMS

CVE-2025-67481

MEDIUM · 6.1 CVSS v3.1 Published 2026-02-03
Fix available
A fix is available. Upgrade to 1.39.16 / 1.43.6 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 (XSS or 'Cross-site Scripting') vulnerability in Wikimedia Foundation MediaWiki. This vulnerability is associated with program files resources/src/mediawiki.JqueryMsg/mediawiki.JqueryMsg.Js. This issue affects MediaWiki: from * before 1.39.16, 1.43.6, 1.44.3, 1.45.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 · high confidence

A stored XSS vulnerability exists in MediaWiki's JqueryMsg JavaScript library (mediawiki.JqueryMsg.js). The library improperly neutralizes user input during web page generation, allowing injection of malicious JavaScript through crafted wiki message content that gets rendered by the JqueryMsg parser.

MitigationUpgrade MediaWiki to version 1.39.16, 1.43.6, 1.44.3, or 1.45.1 or later to receive 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
MediawikiCMS
Affected:>= 1.39.0, < 1.39.16>= 1.43.0, < 1.43.6>= 1.44.0, < 1.44.3= 1.45.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
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. Determine installed MediaWiki version
    Access Special:Version on your wiki or query the API at api.php?action=query&meta=siteinfo&format=json to retrieve the mw version parameter
    Affected if The version listed is >= 1.39.0 and < 1.39.16, OR >= 1.43.0 and < 1.43.6, OR >= 1.44.0 and < 1.44.3, OR equals 1.45.0
  2. Verify JqueryMsg module is loaded
    Check if the mediawiki.jqueryMsg resource is loaded on pages by viewing page source and searching for mediawiki.JqueryMsg or the module in ResourceLoader; alternatively, check includes/ResourceLoader.php or similar for module definitions
    Affected if The JqueryMsg JavaScript module is present and loaded in your MediaWiki installation
  3. Confirm user-generated content rendering
    Determine if your wiki allows users to create or edit pages containing wiki message content that gets processed by the JqueryMsg parser - this includes custom wikitext, templates, or parser functions that invoke message parsing
    Affected if Your wiki permits users to submit or edit content that gets parsed and rendered by the JqueryMsg library (standard wikis with user-editable pages are affected when using vulnerable versions)

Your environment is affected if the installed MediaWiki version falls within any of the vulnerable ranges AND the JqueryMsg module processes user-submitted wiki message content on your site.

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.39.16 / 1.43.6 / 1.44.3 or later
Fixed in 1.39.161.43.61.44.3
Interim mitigation

Upgrade MediaWiki to version 1.39.16, 1.43.6, 1.44.3, or 1.45.1 or later to receive the patch for this vulnerability.

Recommended fix High confidence

Upgrade to the latest patch release in your branch: 1.39.16 (for 1.39.x), 1.43.6 (for 1.43.x), 1.44.3 (for 1.44.x), or 1.45.1 (for 1.45.x)

  1. Backup your MediaWiki database and files before proceeding
  2. Verify your PHP version is compatible with the target MediaWiki version
  3. Download the appropriate MediaWiki release (1.39.16, 1.43.6, 1.44.3, or 1.45.1) from https://www.mediawiki.org/
  4. Extract the new version to a temporary directory
  5. Copy the new files over your existing installation, or use the web updater at /mw-config/ if performing a fresh install
  6. Run the database update script: php maintenance/update.php
  7. Clear any cache (objectcache, message cache) to ensure new JavaScript is loaded
  8. Verify the upgrade was successful by checking Special:Version
Caveat Check release notes for your branch for any configuration or compatibility changes; major version jumps may require testing

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
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
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,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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