dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2025-32079

MEDIUM · 6.5 CVSS v3.1 Published 2025-04-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
Improper Input Validation vulnerability in The Wikimedia Foundation Mediawiki - GrowthExperiments allows HTTP DoS.This issue affects Mediawiki - GrowthExperiments: 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 confidence

Improper input validation in the MediaWiki GrowthExperiments extension allows remote attackers to cause a denial of service via HTTP requests. The vulnerability affects versions 1.39 through 1.43 of the extension.

MitigationUpdate to a patched version of MediaWiki GrowthExperiments if available, or implement proper input validation on HTTP request parameters in the affected extension code to prevent resource exhaustion.

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
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

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 if GrowthExperiments extension is installed
    Look for the GrowthExperiments directory in your MediaWiki extensions folder (commonly extensions/GrowthExperiments), or search for 'GrowthExperiments' in your MediaWiki installation files
    Affected if The extension is not installed, therefore this CVE does not apply
  2. Determine the installed version of the extension
    Read the version information from the extension's composer.json, extension.json, or VERSION file located in the GrowthExperiments directory. Compare the version number to the affected range 1.39 to 1.43
    Affected if The installed version is 1.39, 1.40, 1.41, 1.42, or 1.43, meaning the vulnerable code is present
  3. Verify the extension is enabled in MediaWiki
    Check your MediaWiki LocalSettings.php file for a require_once or wfLoadExtension call referencing GrowthExperiments (for example: require_once "$IP/extensions/GrowthExperiments/GrowthExperiments.php")
    Affected if The extension is enabled and loaded by MediaWiki, exposing the vulnerable code to HTTP requests
  4. Confirm the extension handles HTTP requests
    Examine whether your MediaWiki instance has any GrowthExperiments-related URL endpoints or API routes exposed (typically under /growthexperiments or /api/growth), which would allow remote attackers to send malicious HTTP requests
    Affected if HTTP request handling features of GrowthExperiments are accessible, enabling the input validation flaw to be exploited

Your environment is affected if GrowthExperiments extension is installed with a version between 1.39 and 1.43 and the extension is enabled, exposing HTTP request handling that can be exploited for denial of service.

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

Update to a patched version of MediaWiki GrowthExperiments if available, or implement proper input validation on HTTP request parameters in the affected extension code to prevent resource exhaustion.

Recommended fix Moderate confidence

MediaWiki 1.44 or later (includes fixed GrowthExperiments)

  1. 1. Identify the current MediaWiki version by checking LocalSettings.php or the Special:Version page
  2. 2. Confirm the GrowthExperiments extension version is between 1.39 and 1.43
  3. 3. Plan maintenance window as upgrade may require brief site downtime
  4. 4. Back up the database and all configuration files before proceeding
  5. 5. Update MediaWiki core to version 1.44 or later, which includes the fixed GrowthExperiments extension
  6. 6. Run the update.php maintenance script: php maintenance/update.php
  7. 7. Clear all caches (objectcache, messagestats, etc.)
  8. 8. Verify the GrowthExperiments extension loads correctly via Special:Version
Caveat Minor: Review 1.44 release notes for any GrowthExperiments breaking changes; some newcomer features may have new configuration requirements

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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