Skip to main content
CVE-2025-6592VulnerabilityPublished Updated

CVE-2025-6592: Wikimedia Foundation AbuseFilter · Vulnerability

Affects Wikimedia Foundation AbuseFilterSource CVE Database V5

0

Not known to be exploited · CVSS 2.1 Low : upgrade to 1.43.2 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score
2.1Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.43.2
CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Upgrade Wikimedia Foundation AbuseFilter to 1.43.2.

Affected software

ProductAffectedFixed in
Wikimedia FoundationAbuseFilterAffected
  • ≥ fe0b1cb9e9691faf4d8d9bd80646589f6ec37615, < 1.43.2, 1.44.0
Fixed in
  • 1.43.2

AI-suggested

European organizations should implement the following specific mitigations: 1) Immediately review and restrict administrative privileges related to AbuseFilter and AuthManager.php to the minimum necessary users. 3) Conduct code audits and configuration reviews of AbuseFilter implementations to detect any unauthorized changes or suspicious activity. 4) Employ network segmentation and access controls to limit exposure of Wikimedia infrastructure components to trusted networks only. 5) Use logging and alerting mechanisms to detect anomalous access patterns or privilege escalations within AbuseFilter modules. 6) Engage with the Wikimedia community to share threat intelligence and best practices for securing AbuseFilter deployments. 7) Consider deploying additional application-layer security controls such as Web Application Firewalls (WAFs) to detect and block exploitation attempts targeting authorization flaws. These measures go beyond generic advice by focusing on privilege management, monitoring, and community collaboration specific to the Wikimedia AbuseFilter context.

Description

Vulnerability in Wikimedia Foundation AbuseFilter. This vulnerability is associated with program files includes/auth/AuthManager.Php. This issue affects AbuseFilter: from fe0b1cb9e9691faf4d8d9bd80646589f6ec37615 before 1.43.2, 1.44.0.

References

Community reviews

Loading reviews…