Wikimedia AbuseFilter up to 1.45.x/1.45.3/1.44.5/1.43.8 QueryAbuseFilters.Php information disclosure

Summaryinfo

A vulnerability classified as problematic has been found in Wikimedia AbuseFilter up to 1.45.x/1.45.3/1.44.5/1.43.8. This issue affects some unknown processing of the file includes/Api/QueryAbuseFilters.Php. This manipulation causes information disclosure. This vulnerability is tracked as CVE-2026-58027. The attack is possible to be carried out remotely. No exploit exists. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability was found in Wikimedia AbuseFilter up to 1.45.x/1.45.3/1.44.5/1.43.8. It has been declared as problematic. Affected by this vulnerability is some unknown processing of the file includes/Api/QueryAbuseFilters.Php. The manipulation with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality. The summary by CVE is:

Exposure of Sensitive Information to an Unauthorized Actor vulnerability in Wikimedia Foundation AbuseFilter. This vulnerability is associated with program files includes/Api/QueryAbuseFilters.Php. This issue affects AbuseFilter: from * before 1.46.0, 1.45.4, 1.44.6, 1.43.9.

The advisory is shared at phabricator.wikimedia.org. This vulnerability is known as CVE-2026-58027 since 06/27/2026. The exploitation appears to be easy. The attack can be launched remotely. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1592 for this issue.

By approaching the search of inurl:includes/Api/QueryAbuseFilters.Php it is possible to find vulnerable targets with Google Hacking.

Upgrading to version 1.46.0, 1.45.4, 1.44.6 or 1.43.9 eliminates this vulnerability.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• Content Management System

Vendor

• Wikimedia

Name

• AbuseFilter

Version

• 1.0
• 1.1
• 1.2
• 1.3
• 1.4
• 1.5
• 1.6
• 1.7
• 1.8
• 1.9
• 1.10
• 1.11
• 1.12
• 1.13
• 1.14
• 1.15
• 1.16
• 1.17
• 1.18
• 1.19
• 1.20
• 1.21
• 1.22
• 1.23
• 1.24
• 1.25
• 1.26
• 1.27
• 1.28
• 1.29
• 1.30
• 1.31
• 1.32
• 1.33
• 1.34
• 1.35
• 1.36
• 1.37
• 1.38
• 1.39
• 1.40
• 1.41
• 1.42
• 1.43
• 1.43.0
• 1.43.1
• 1.43.2
• 1.43.3
• 1.43.4
• 1.43.5
• 1.43.6
• 1.43.7
• 1.43.8
• 1.44
• 1.44.0
• 1.44.1
• 1.44.2
• 1.44.3
• 1.44.4
• 1.44.5
• 1.45
• 1.45.0
• 1.45.1
• 1.45.2
• 1.45.3

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion