dbcve.org
MediawikiCMS

CVE-2025-61642

MEDIUM · 6.1 CVSS v3.1 Published 2026-02-03
Fix available
A fix is available. Upgrade to 1.39.14 / 1.43.4 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/htmlform/CodexHTMLForm.Php, includes/htmlform/fields/HTMLButtonField.Php. This issue affects MediaWiki: from * before 1.39.14, 1.43.4, 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

Cross-site scripting (XSS) vulnerability in MediaWiki's HTML form rendering components (CodexHTMLForm and HTMLButtonField). The vulnerability allows malicious script injection through improperly sanitized form input fields during page generation.

MitigationUpgrade MediaWiki to version 1.39.14, 1.43.4, 1.44.1 or later to receive the patch for proper input sanitization in the affected HTML form components.

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.14>= 1.43.0, < 1.43.4= 1.44.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. Check MediaWiki version
    Access Special:Version on your wiki, or inspect includes/Defines.php for the $wgVersion variable, or run 'composer show mediawiki/core' to determine the installed version
    Affected if The installed version is less than 1.39.14, OR between 1.43.0 and 1.43.3 inclusive, OR exactly 1.44.0
  2. Locate CodexHTMLForm component
    Search the codebase for files named CodexHTMLForm.php or containing class CodexHTMLForm to verify this component exists in your installation
    Affected if The CodexHTMLForm.php file exists in your MediaWiki installation and is being used to render forms
  3. Locate HTMLButtonField component
    Search the codebase for files named HTMLButtonField.php or containing class HTMLButtonField to verify this component exists in your installation
    Affected if The HTMLButtonField.php file exists in your MediaWiki installation and is being used to render forms with button fields
  4. Check for custom or third-party forms using affected components
    Search your extensions or skin directories for uses of CodexHTMLForm or HTMLButtonField classes in form definitions, particularly any that accept user-supplied input
    Affected if Your wiki runs extensions or skins that utilize CodexHTMLForm or HTMLButtonField to render form fields with user-accessible input

Your environment is affected if the installed MediaWiki version falls within the vulnerable ranges AND your wiki uses CodexHTMLForm or HTMLButtonField components to render forms that process user input.

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.14 / 1.43.4 or later
Fixed in 1.39.141.43.4
Interim mitigation

Upgrade MediaWiki to version 1.39.14, 1.43.4, 1.44.1 or later to receive the patch for proper input sanitization in the affected HTML form components.

Recommended fix High confidence

1.39.14 (for 1.39.x branch), 1.43.4 (for 1.43.x branch), or 1.44.1 (for 1.44.x branch)

  1. 1. Identify the current MediaWiki version by checking LocalSettings.php or the Special:Version page
  2. 2. If running version 1.39.x: upgrade to version 1.39.14
  3. 3. If running version 1.43.x: upgrade to version 1.43.4
  4. 4. If running version 1.44.0: upgrade to version 1.44.1
  5. 5. After upgrade, clear any caches and verify the installation works correctly
  6. 6. Test that the HTMLButtonField and CodexHTMLForm components function properly
Caveat Standard MediaWiki minor version upgrades typically have minimal breaking changes; review the release notes for your target version for any migration notes

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
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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