CVE-2025-62668
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 · uneditedIncorrect Default Permissions vulnerability in The Wikimedia Foundation Mediawiki - GrowthExperiments Extension allows Resource Leak Exposure.This issue affects Mediawiki - GrowthExperiments Extension: from master before 1.39.
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 confidenceIncorrect default permissions in MediaWiki's GrowthExperiments Extension allow unauthorized access to resources due to overly permissive file or directory settings, leading to potential resource leak exposure.
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 checksWork through these to decide whether this CVE applies to you.
-
Verify GrowthExperiments extension is enabledCheck your MediaWiki configuration file (LocalSettings.php) for the line: wfLoadExtension( 'GrowthExperiments' ); or look for the extension in your wiki's Special:Version pageAffected if The extension is installed and enabled in MediaWiki
-
Determine GrowthExperiments extension versionCheck the version file in your extension directory: {mw-install-path}/extensions/GrowthExperiments/extension.json or composer.json, or run: composer show mediawiki/growth-experiments on your serverAffected if The installed version is earlier than 1.39 (the fixed release)
-
Inspect GrowthExperiments directory permissionsRun: ls -la {mw-install-path}/extensions/GrowthExperiments/ to list all files and directories and their permission settingsAffected if Any file or directory shows permissions wider than 755 (for directories) or 644 (for files), such as 777 or world-readable settings
-
Check data and cache directory permissionsExamine directories used by GrowthExperiments for caching or data storage: ls -la {mw-install-path}/images/ and any custom GrowthExperiments data paths configured in LocalSettings.phpAffected if These directories have overly permissive settings allowing unauthorized read or write access
-
Review configuration file permissionsCheck LocalSettings.php and any GrowthExperiments-specific config files: ls -la {mw-install-path}/extensions/GrowthExperiments/config/Affected if Configuration files are world-readable or have permissive access controls
Your environment is affected if GrowthExperiments extension is enabled with a version prior to 1.39, OR if any files/directories in the extension path have overly permissive permissions (wider than standard restrictive settings).
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpdate GrowthExperiments extension to version 1.39 or later and review file/directory permissions to ensure restrictive access controls are in place.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-62668 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-62668 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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