dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2025-32076

MEDIUM · 6.9 CVSS v4.0 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 →
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
Improper Input Validation vulnerability in The Wikimedia Foundation Mediawiki - Visual Data Extension allows HTTP DoS.This issue affects Mediawiki - Visual Data 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 confidence

The Visual Data Extension in MediaWiki versions 1.39-1.43 contains an improper input validation vulnerability that allows remote attackers to cause HTTP denial of service via specially crafted requests. The vulnerability stems from the extension's failure to properly validate or sanitize user inputs before processing them, potentially allowing resource exhaustion or service disruption.

MitigationUpgrade the Visual Data Extension to the latest version that includes the fix for CVE-2025-32076. If an immediate upgrade is not possible, implement input validation and rate limiting at the web server or application level to mitigate DoS attempts.

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. Verify MediaWiki is installed
    Check for MediaWiki installation by looking for the presence of the MediaWiki software directory or the existence of the 'LocalSettings.php' configuration file in the web server's document root.
    Affected if MediaWiki is not installed or no MediaWiki instance is found.
  2. Identify Visual Data Extension presence
    Look for the VisualData extension directory within the MediaWiki 'extensions' folder. This is typically located at /path/to/mediawiki/extensions/VisualData/ and should contain the extension's PHP files.
    Affected if The Visual Data Extension directory does not exist in the MediaWiki extensions folder.
  3. Check if Visual Data Extension is enabled
    Open the MediaWiki 'LocalSettings.php' file and search for a line containing 'wfLoadExtension' or 'enableExtension' that references 'VisualData' or 'Visual Data Extension'.
    Affected if The extension is not loaded in LocalSettings.php (no 'wfLoadExtension' call for VisualData).
  4. Determine MediaWiki core version
    Access the Special:Version page on the wiki (e.g., https://yourwiki.example.org/wiki/Special:Version) or check the 'includes/Defines.php' file for the MW_VERSION constant, or run 'php maintenance/run.php version' if available.
    Affected if The installed MediaWiki version falls within the range 1.39 through 1.43.
  5. Verify Visual Data Extension version
    On the Special:Version page, locate the entry for Visual Data Extension to confirm its specific version number, or check the 'extension.json' file within the VisualData extension directory.
    Affected if The Visual Data Extension version corresponds to the vulnerable MediaWiki versions 1.39-1.43.

A user is affected if they have MediaWiki versions 1.39-1.43 running with the Visual Data Extension enabled and the extension has not been patched to address the input validation vulnerability.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade the Visual Data Extension to the latest version that includes the fix for CVE-2025-32076. If an immediate upgrade is not possible, implement input validation and rate limiting at the web server or application level to mitigate DoS attempts.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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 locally
dbcve dependency scanner

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