# CVE-2025-61649: UserInfoCard: Check that performing user has permission to view log entries for number of past blocks

> An attacker can view log entries for past blocks without proper permission checks, exposing sensitive user data.

- **Severity:** Low 1.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:U`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 3 Feb 2026
- **Updated:** 3 Mar 2026
- **Also known as:** GHSA-v687-vxc5-92hv

## What is CVE-2025-61649?

CVE-2025-61649 is a low-severity missing authorization vulnerability in Wikimedia Foundation CheckUser, published on 3 Feb 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Vulnerability in Wikimedia Foundation CheckUser. This vulnerability is associated with program files src/Services/CheckUserUserInfoCardService.Php.

This issue affects CheckUser: from 7cedd58781d261f110651b6af4f41d2d11ae7309.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

No fix has been published for CVE-2025-61649 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-61649 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-61649 is a low-severity missing authorization vulnerability in Wikimedia Foundation CheckUser, published on 3 Feb 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-61649 in the wild and no public exploit code.

Affected product: Wikimedia Foundation CheckUser. 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-61649/ (Markdown: https://insights.sbomify.com/CVE-2025-61649/index.md)
```

## Sources

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

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