CVE-2025-61639
Information Disclosure in MediaWiki Components Allows Unauthorized Access
Publication date: 2026-02-03
Last updated on: 2026-03-16
Assigner: wikimedia-foundation
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| mediawiki | mediawiki | to 1.39.14 (exc) |
| mediawiki | mediawiki | From 1.39.15 (inc) to 1.43.4 (exc) |
| mediawiki | mediawiki | From 1.43.5 (inc) to 1.44.1 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-200 | The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in Wikimedia Foundation MediaWiki involves the exposure of sensitive information to unauthorized actors. It is related to certain program files (includes/logging/ManualLogEntry.Php, includes/recentchanges/RecentChangeFactory.Php, includes/recentchanges/RecentChangeStore.Php) and affects versions before 1.39.14, 1.43.4, and 1.44.1.
How can this vulnerability impact me? :
The vulnerability can lead to unauthorized access to sensitive information within MediaWiki, potentially compromising confidentiality and privacy of data managed by the system.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability involves the exposure of sensitive information to unauthorized actors in Wikimedia Foundation MediaWiki. Such exposure can potentially lead to non-compliance with data protection regulations like GDPR and HIPAA, which require the protection of sensitive personal and health information from unauthorized access.
However, specific impacts on compliance with these standards are not detailed in the provided information.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
I don't know