# CVE-2025-6592: Information disclosure in AbuseFilter

> Attackers can view sensitive IP and username associations in AbuseLog when converting temporary accounts to permanent ones, exposing user privacy data.

- **Severity:** Low 2.1 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 Feb 2026
- **Updated:** 4 Feb 2026
- **Also known as:** DEBIAN-CVE-2025-6592, GHSA-9r44-56w8-gqrx, UBUNTU-CVE-2025-6592

## What is CVE-2025-6592?

CVE-2025-6592 is a low-severity vulnerability in Wikimedia Foundation AbuseFilter, published on 2 Feb 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official 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.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2025-6592?


## How do I fix CVE-2025-6592?

Upgrade to a fixed version.

## Is CVE-2025-6592 being exploited?

There is no known exploitation of CVE-2025-6592 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-6592 and fix it if it is affected.

What it is: CVE-2025-6592 is a low-severity vulnerability in Wikimedia Foundation AbuseFilter, published on 2 Feb 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-6592 in the wild and no public exploit code.

Affected product: Wikimedia Foundation AbuseFilter. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-6592/ (Markdown: https://insights.sbomify.com/CVE-2025-6592/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-6592
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-6592
- OSV: https://osv.dev/vulnerability/CVE-2025-6592

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-6592/
Summaries are generated and may contain mistakes; the official description above is the record.