dbcve.org
MediawikiCMS

CVE-2025-61641

MEDIUM · 6.1 CVSS v3.1 Developing 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
Vulnerability in Wikimedia Foundation MediaWiki. This vulnerability is associated with program files includes/api/ApiQueryAllPages.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 · low confidence
Developing — this CVE was published recently and its authoritative NVD entry is still being established, so we're holding a technical summary until the source data settles rather than publish something unreliable. Re-checking after 2026-07-30.

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

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
Recommended fix High confidence

Upgrade to 1.39.14 (if on 1.39.x), 1.43.4 (if on 1.43.x), or 1.44.1 (if on 1.44.x) - preferably the latest stable release in your branch

  1. 1. Check current MediaWiki version by examining includes/Defines.php or the Special:Version page
  2. 2. Determine which upgrade path applies: for 1.39.x branch upgrade to 1.39.14+, for 1.43.x branch upgrade to 1.43.4+, for 1.44.x branch upgrade to 1.44.1+
  3. 3. Review the MediaWiki release notes for your target version for any breaking changes or required database updates
  4. 4. Create a full backup of the database and files before upgrading
  5. 5. In a staging environment, apply the upgrade and run the update.php maintenance script: php maintenance/update.php
  6. 6. Verify the ApiQueryAllPages.php file has been updated (check file modification date matches the new version)
  7. 7. Test the API endpoint to confirm normal operation: api.php?action=query&list=allpages
  8. 8. Deploy the tested upgrade to production
Caveat Point releases typically include only bug/security fixes; minor breaking changes may occur if skipping multiple versions - review release notes

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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