dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2025-32069

MEDIUM · 5.4 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 →
58/100
Remediation priority · Elevated
Remotely reachable

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 - Wikibase Media Info Extension allows Cross-Site Scripting (XSS).This issue affects Mediawiki - Wikibase Media Info 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 · high confidence

This is a cross-site scripting (XSS) vulnerability in the Wikibase Media Info Extension for MediaWiki caused by improper input validation. The vulnerability allows attackers to inject malicious scripts into web pages that are rendered for other users, potentially compromising user sessions or stealing sensitive information.

MitigationUpgrade the Wikibase Media Info Extension to a version beyond 1.43 that contains the fix, or apply any available security patches. Until then, implement content security policy headers and sanitize user-supplied input in the affected component.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Wikibase Media Info Extension is installed
    Examine your MediaWiki installation's extensions/ directory for the WikibaseMediaInfo folder, or check LocalSettings.php for any 'wfLoadExtension' or 'requireOnce' entries referencing 'WikibaseMediaInfo'
    Affected if The extension directory exists and the extension is loaded in MediaWiki configuration
  2. Identify the installed version of the Wikibase Media Info Extension
    Visit your wiki's Special:Version page and locate the Wikibase MediaInfo entry in the extensions list, or directly read the extension.json or composer.json file within the WikibaseMediaInfo directory
    Affected if Version is 1.43 or any version lower than the fixed release (the fix is in versions beyond 1.43)
  3. Verify the MediaInfo component is actively enabled
    Check LocalSettings.php to confirm the extension is not commented out, and attempt to access MediaInfo functionality on your wiki to confirm it renders user-supplied data
    Affected if The extension is loaded and functional, allowing user input to be processed through MediaInfo

You are affected if Wikibase Media Info Extension version 1.43 or lower is installed and the MediaInfo feature is enabled in your MediaWiki environment, exposing users to XSS via unvalidated input.

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 Wikibase Media Info Extension to a version beyond 1.43 that contains the fix, or apply any available security patches. Until then, implement content security policy headers and sanitize user-supplied input in the affected component.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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