Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain valid low-privilege account
-
DeliveryAuthenticate to Wikimedia instance
-
ExploitNavigate to AbuseFilter interface
-
ExecutionPerform targeted user interaction
-
PersistTrigger information disclosure
-
ImpactExfiltrate limited confidential data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V2 - Validation and Business Logic Input validation, allowlisting
|
| Exploitation Conditions | Exploitation requires authentication (PR:L, low-privilege account or above), active user interaction (UI:P), high attack complexity (AC:H), and partial temporal occurrence (AT:P) suggesting the issue manifests under specific timing, configuration, or environmental conditions. The vulnerability does not affect default deployments without user action - an attacker must have a valid low-privilege account and must actively engage with AbuseFilter features through the network interface to trigger the disclosure. |
| Impact | Real-world risk is low despite the vulnerability being publicly documented. CVSS score of 2.1 is at the absolute minimum severity threshold, reflecting multiple limiting factors: required authentication (PR:L), user interaction (UI:P), and attack complexity high (AC:H) with partial temporal occurrence (AT:P). EPSS score and KEV status are not available, but the information disclosure classification and low-privilege requirement suggest this is not a priority for widespread exploitation. The impact is limited to confidentiality (VI:L/VC:L) with no integrity or availability impact, and scope is not changed, indicating the attacker cannot escalate beyond their existing permissions. This appears to be a legitimate but low-impact vulnerability affecting authenticated users who must perform specific interactions to trigger the leak. |
| Exploit ScenarioDerived | An authenticated user with low-privilege access logs into a Wikimedia installation running vulnerable AbuseFilter and performs specific interactions with filter configuration or execution logic, causing the system to expose limited confidential information related to filter rules or internal processing. The interaction may involve crafted inputs to filter form fields or deliberate sequencing of filter operations that triggers the information disclosure. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – May 11, 2026
Information disclosure in Wikimedia Foundation AbuseFilter allows low-privileged authenticated users with user interaction to access limited confidential data through a network vector. The vulnerability affects AbuseFilter versions prior to 1.43.7, 1.44.4, and 1.45.2, with very low CVSS score (2.1) indicating minimal real-world impact but potential for sensitive information leakage in filtered content or filter logic contexts.
RemediationAI
Upgrade AbuseFilter to version 1.43.7, 1.44.4, or 1.45.2 or later, depending on which release track is in use. Vendor-released patches are available per Wikimedia Foundation. For environments unable to patch immediately, restrict access to filter administration and management interfaces to trusted administrators, and monitor filter-related logs for suspicious user interactions that may indicate exploitation attempts. Review access controls on accounts with low-privilege filter permissions to ensure least-privilege principles are enforced.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
AbuseFilter is a content-moderation tool deployed in Wikimedia installations that uses rule-based filtering to identify and manage abusive contributions. The vulnerability appears to involve improper access controls or information exposure in the filter mechanism itself, likely triggered through a network interface requiring low-privilege authentication and user interaction. CPE cpe:2.3:a:wikimedia_foundation:abusefilter:*:*:*:*:*:*:*:* confirms the affected component. While specific CWE is not provided, the CVSS 4.0 vector indicating confidentiality impact (VC:L/VI:L) and scope limitation (S:N) suggests a logic flaw in access control or data exposure in filter operations.
Know when Abusefilter gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N/S:N/AU:Y
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
Lifecycle Timeline
4DescriptionCVE.org
Vulnerability in Wikimedia Foundation AbuseFilter.
This issue affects AbuseFilter: from * before 1.43.7, 1.44.4, 1.45.2.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
More in Abusefilter
View allSensitive abuse filter configuration data in Wikimedia Foundation's AbuseFilter MediaWiki extension is exposed to authen
An issue was discovered in the AbuseFilter extension through 1.34 for MediaWiki. Rated medium severity (CVSS 5.3), this
An issue was discovered in the AbuseFilter extension through 1.34 for MediaWiki. Rated medium severity (CVSS 5.3), this
EUVD-2026-29058
GHSA-5qc5-wp75-wxgx
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB