# CVE-2025-61654: UserInfoCard: Do permission checking when getting counts of global and local edits, new articles and thanks

> Attackers can bypass permission checks to view counts of edits, articles, and thanks in the MediaWiki Thanks extension.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Feb 2026
- **Updated:** 3 Mar 2026
- **Also known as:** DEBIAN-CVE-2025-61654, GHSA-gcpp-j34q-494f, UBUNTU-CVE-2025-61654

## What is CVE-2025-61654?

CVE-2025-61654 is a missing authorization vulnerability in Wikimedia Foundation Thanks, published on 3 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Vulnerability in Wikimedia Foundation Thanks. This vulnerability is associated with program files includes/ThanksQueryHelper.Php.

This issue affects Thanks: from * before 1.43.4, 1.44.1.

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

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


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

Upgrade to a fixed version.

## Is CVE-2025-61654 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-61654 is a missing authorization vulnerability in Wikimedia Foundation Thanks, published on 3 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-61654 in the wild and no public exploit code.

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

## Sources

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

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