MediawikiCMS

CVE-2025-67483

MEDIUM · 6.1 CVSS v3.1 Published 2026-02-03
Fix available
A fix is available. Upgrade to 1.43.6 / 1.44.3 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.Page.Preview.Js. This issue affects MediaWiki: from * before 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

Cross-site scripting (XSS) vulnerability in MediaWiki's page preview functionality (mediawiki.Page.Preview.Js) allows injection of malicious scripts through improper neutralization of user input during web page generation.

MitigationUpgrade MediaWiki to version 1.43.6, 1.44.3, 1.45.1 or later to obtain the patched version of the page preview component.

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.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. Identify installed MediaWiki version
    Check the VERSION file in the MediaWiki root directory, or look for the MW_VERSION constant in includes/Defines.php, or view Special:Version on your wiki
    Affected if The version is 1.43.0 through 1.43.5, 1.44.0 through 1.44.2, or exactly 1.45.0
  2. Confirm page preview functionality is enabled
    Check your LocalSettings.php for $wgPagePreviewEnable being set to true (or not set to false, as previews are enabled by default in affected versions)
    Affected if Page previews are enabled in your MediaWiki installation
  3. Verify the mediawiki.Page.Preview.Js module is present
    Access your wiki's ResourceLoader debug endpoint or check the skins/.../resources folder for the presence of PagePreview.js module files
    Affected if The PagePreview JavaScript module is loaded in your installation

Your environment is affected if you are running any of the vulnerable MediaWiki versions (1.43.0-1.43.5, 1.44.0-1.44.2, or 1.45.0) AND page previews are enabled.

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.6 / 1.44.3 or later
Fixed in 1.43.61.44.3
Interim mitigation

Upgrade MediaWiki to version 1.43.6, 1.44.3, 1.45.1 or later to obtain the patched version of the page preview component.

Recommended fix High confidence

MediaWiki 1.43.6, 1.44.3, or 1.45.1 (depending on your current branch)

  1. 1. Back up your MediaWiki database and files before upgrading
  2. 2. Identify your current MediaWiki version (usually in includes/Defines.php or Special:Version)
  3. 3. If running 1.43.x: upgrade to MediaWiki 1.43.6 or later
  4. 4. If running 1.44.x: upgrade to MediaWiki 1.44.3 or later
  5. 5. If running 1.45.0: upgrade to MediaWiki 1.45.1 or later
  6. 6. Clear any server-side caches (PHP opcache, mediawiki objectcache) after upgrade
  7. 7. Verify the upgrade was successful and the XSS vulnerability is resolved
Caveat Review MediaWiki release notes for your target version for any configuration or compatibility changes

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
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-67483 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-67483 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