dbcve.org
Incorrect Default PermissionsWeakness · CWE-276

CVE-2025-62661

MEDIUM · 6.9 CVSS v4.0 Published 2025-10-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
Incorrect Default Permissions vulnerability in The Wikimedia Foundation Mediawiki - Thanks Extension, Mediawiki - Growth Experiments Extension allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Mediawiki - Thanks Extension, Mediawiki - Growth Experiments Extension: from 1.43 before 1.44.

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 · moderate confidence

A permissions vulnerability in MediaWiki's Thanks and Growth Experiments extensions (versions 1.43 through versions prior to 1.44) allows users to access functionality that should be restricted by Access Control Lists. The extensions have incorrect default permission settings that fail to properly constrain user access to certain features.

MitigationUpgrade both extensions to version 1.44 or later, and audit user group permissions to ensure ACLs are properly enforcing access controls.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:L/SI:L/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 core version
    Visit Special:Version on your wiki or check includes/Defines.php for the MW_VERSION constant
    Affected if Core version is 1.43.x or earlier than 1.44.0 and extensions are installed
  2. Check Thanks extension version
    Visit Special:Version to see installed extensions and their versions, or check the extension's version file in the extensions/Thanks directory
    Affected if Thanks extension is installed and version is 1.43.x or prior to 1.44.0
  3. Check Growth Experiments extension version
    Visit Special:Version to see installed extensions and their versions, or check the extension's version file in the extensions/GrowthExperiments directory
    Affected if Growth Experiments extension is installed and version is 1.43.x or prior to 1.44.0
  4. Verify extensions are enabled in LocalSettings.php
    Examine your LocalSettings.php file for lines containing wfLoadExtension('Thanks') or wfLoadExtension('GrowthExperiments')
    Affected if Either extension is enabled in the configuration
  5. Inspect default user rights for affected extensions
    Check LocalSettings.php or extension-specific configuration for user rights settings related to thanks or growth features. Look for $wgGroupPermissions configurations
    Affected if Default permissions are in use and ACL restrictions are not explicitly configured for these extension features

Your environment is affected if the Thanks extension, the Growth Experiments extension, or both are installed at version 1.43.x or any version prior to 1.44.0, with default permission settings that fail to enforce ACL restrictions.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade both extensions to version 1.44 or later, and audit user group permissions to ensure ACLs are properly enforcing access controls.

Recommended fix Moderate confidence

MediaWiki extensions 1.44

  1. Upgrade MediaWiki Thanks Extension to version 1.44 or later
  2. Upgrade MediaWiki Growth Experiments Extension to version 1.44 or later

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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