dbcve.org
MediawikiCMS

CVE-2025-61645

MEDIUM · 6.1 CVSS v3.1 Published 2026-02-03
Fix available
A fix is available. Upgrade to 1.44.1 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 includes/pager/CodexTablePager.Php. This issue affects MediaWiki: from * before 1.44.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 in MediaWiki's CodexTablePager component allows injection of malicious scripts through improper input neutralization in includes/pager/CodexTablePager.php. The vulnerability affects MediaWiki versions prior to 1.44.1 and could allow authenticated attackers to execute arbitrary JavaScript in the context of other users' sessions.

MitigationUpgrade to MediaWiki 1.44.1 or later. As an interim measure, restrict access to affected functionality and implement content security policy headers to mitigate XSS impact.

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.44.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
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 version
    Locate and inspect the MediaWiki version file, commonly found in includes/Defines.php or retrieved via the Special:Version page in the web interface
    Affected if The installed version is earlier than 1.44.1
  2. Verify CodexTablePager component presence
    Inspect the file includes/pager/CodexTablePager.php in the MediaWiki installation directory
    Affected if The file exists in the installation, indicating the vulnerable component is present
  3. Identify usage of CodexTablePager
    Search the codebase for any references to CodexTablePager in extension files, skins, or custom code that instantiate this class
    Affected if Any extension, skin, or custom code actively uses or instantiates the CodexTablePager class
  4. Confirm authenticated access exists
    Verify that the wiki allows user accounts and has features that utilize table pagination with the CodexTablePager component
    Affected if The wiki has user registration enabled and any feature using CodexTablePager is accessible to authenticated users

A user is affected if their MediaWiki installation version is below 1.44.1 AND the CodexTablePager component is present and actively used in their environment.

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.44.1 or later
Fixed in 1.44.1
Interim mitigation

Upgrade to MediaWiki 1.44.1 or later. As an interim measure, restrict access to affected functionality and implement content security policy headers to mitigate XSS impact.

Recommended fix High confidence

MediaWiki 1.44.1

  1. 1. Back up the MediaWiki database before starting the upgrade process
  2. 2. Back up all MediaWiki installation files, including LocalSettings.php and any custom extensions
  3. 3. Download MediaWiki 1.44.1 from the official MediaWiki releases page (https://www.mediawiki.org/wiki/Download)
  4. 4. Extract the new version to a temporary directory
  5. 5. Replace the old MediaWiki files with the new version, preserving LocalSettings.php and any custom configuration
  6. 6. Run the database update script (maintenance/update.php) from the command line: php maintenance/update.php
  7. 7. Clear the MediaWiki object cache (run php maintenance/runJobs.php if applicable)
  8. 8. Verify the installation by accessing the wiki and checking Special:Version
Caveat Minor/patch update within 1.44.x branch - minimal breaking changes expected, but always test in staging first

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
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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