CVE-2025-32067
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 · uneditedImproper Input Validation vulnerability in The Wikimedia Foundation Mediawiki - Growth Experiments Extension allows Cross-Site Scripting (XSS).This issue affects Mediawiki - Growth Experiments Extension: from 1.39 through 1.43.
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 confidenceCross-Site Scripting (XSS) vulnerability in MediaWiki's Growth Experiments extension caused by improper input validation. The vulnerability exists in versions 1.39 through 1.43, where user-supplied input is not adequately sanitized before being rendered in web pages, allowing execution of malicious scripts in the context of the victim's browser.
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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm MediaWiki installationLocate the MediaWiki installation directory and check for the presence of the Growth Experiments extension in the 'extensions/GrowthExperiments' folderAffected if The Growth Experiments extension folder exists in the MediaWiki installation
-
Identify Growth Experiments versionCheck the version file or composer.json in the extensions/GrowthExperiments directory, or run 'composer show' if dependencies are managed that wayAffected if The installed version falls within the range 1.39.0 to 1.43.x inclusive
-
Verify extension is enabledExamine the MediaWiki 'LocalSettings.php' file for a line containing 'wfLoadExtension' or 'enableExtension' that loads the GrowthExperiments extensionAffected if The extension is loaded and enabled in the MediaWiki configuration
-
Check for manual patchesSearch the extension PHP files for custom input sanitization functions or XSS filters that may have been applied manually as a workaroundAffected if No custom sanitization code is found in the extension files and the version is in the affected range
-
Audit user input pathwaysReview the extension's configuration for features that accept user-provided content (such as mentor dashboards, onboarding tasks, or community configuration), and check if these are accessible to unauthenticated or low-privileged usersAffected if User-facing features in the extension accept input and the extension version is unpatched
A user is affected if the Growth Experiments extension is installed and enabled in MediaWiki and its version is 1.39.0 through 1.43.x without any applied custom patches.
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 dataUpgrade the Growth Experiments extension to the latest patched version that addresses this vulnerability. If an immediate patch is unavailable, implement output encoding and input validation on all user-provided data within the extension.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-32067 — 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-32067 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