Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-6927: Vulnerability in Wikimedia Foundation MediaWiki

0
Low
VulnerabilityCVE-2025-6927cvecve-2025-6927
Published: Mon Feb 02 2026 (02/02/2026, 22:55:09 UTC)
Source: CVE Database V5
Vendor/Project: Wikimedia Foundation
Product: MediaWiki

Description

Vulnerability in Wikimedia Foundation MediaWiki. This vulnerability is associated with program files includes/specials/pagers/BlockListPager.Php, includes/api/ApiQueryBlocks.Php. This issue affects MediaWiki: from >= 1.42.0 before 1.39.13, 1.42.7 1.43.2, 1.44.0.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 03/03/2026, 18:30:14 UTC

Technical Analysis

CVE-2025-6927 is a directory traversal vulnerability identified in the MediaWiki software maintained by the Wikimedia Foundation. The vulnerability specifically affects the program files includes/specials/pagers/BlockListPager.Php and includes/api/ApiQueryBlocks.Php. MediaWiki versions from 1.42.0 and certain other versions before 1.39.13, 1.42.7, 1.43.2, and 1.44.0 are impacted. The vulnerability is classified under CWE-22, indicating improper restriction of file paths, which can allow an attacker to access files outside the intended directory structure. According to the CVSS 4.0 vector, the attack vector is network-based (AV:N), with low attack complexity (AC:L), no privileges required (PR:N), but user interaction is necessary (UI:P). The impact on confidentiality is low (VC:L), with no impact on integrity or availability. No known exploits are currently in the wild, and no patches have been linked yet. The vulnerability could allow an attacker to read sensitive files or data that should be restricted, potentially leading to information disclosure. However, the requirement for user interaction and the low impact on confidentiality limit the severity. The vulnerability is published and tracked by the Wikimedia Foundation, which suggests that fixes or mitigations may be forthcoming. Organizations using affected MediaWiki versions should monitor for official patches and updates.

Potential Impact

The potential impact of CVE-2025-6927 is primarily limited to unauthorized information disclosure due to directory traversal. Attackers could exploit this vulnerability to access files outside the intended directories, potentially exposing sensitive configuration files, user data, or other restricted content. While the confidentiality impact is low, any leakage of sensitive information could aid further attacks or compromise user privacy. The vulnerability does not affect data integrity or availability, so it is unlikely to cause service disruption or data manipulation. Because exploitation requires user interaction, the attack surface is reduced, limiting widespread automated exploitation. However, organizations relying on MediaWiki for internal knowledge bases, documentation, or public-facing wikis could face reputational damage or compliance issues if sensitive data is exposed. The lack of known exploits in the wild reduces immediate risk, but the presence of the vulnerability in widely deployed versions means that attackers could develop exploits in the future. Overall, the impact is low but non-negligible, especially for organizations with sensitive content hosted on MediaWiki platforms.

Mitigation Recommendations

To mitigate CVE-2025-6927, organizations should: 1) Monitor official Wikimedia Foundation channels for patches or security updates addressing this vulnerability and apply them promptly once available. 2) Review and restrict user permissions on MediaWiki installations to minimize the risk of exploitation, especially limiting access to untrusted users or anonymous interactions. 3) Implement web application firewalls (WAFs) with rules designed to detect and block directory traversal attempts targeting the affected endpoints (BlockListPager.Php and ApiQueryBlocks.Php). 4) Conduct regular security audits and code reviews of custom MediaWiki extensions or configurations to ensure no additional path traversal weaknesses exist. 5) Employ strict input validation and sanitization on any user-supplied parameters related to file paths or API queries. 6) Limit exposure of MediaWiki instances to trusted networks or VPNs where feasible to reduce attack surface. 7) Monitor logs for unusual access patterns or attempts to access unauthorized files. These steps go beyond generic advice by focusing on proactive monitoring, access control, and layered defenses tailored to the specific vulnerable components.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
wikimedia-foundation
Date Reserved
2025-06-30T14:30:22.357Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 69813004f9fa50a62f63a381

Added to database: 2/2/2026, 11:15:16 PM

Last enriched: 3/3/2026, 6:30:14 PM

Last updated: 3/26/2026, 9:33:54 AM

Views: 37

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses