# CVE-2025-67646: TableProgressTracking's missing CSRF protection allows unauthorized state changes

> An attacker can force authenticated users to delete or modify table progress data via a malicious webpage due to missing CSRF protection.

- **Severity:** Low 3.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 Dec 2025
- **Updated:** 11 Dec 2025
- **Also known as:** GHSA-j24f-hw6w-cq78

## What is CVE-2025-67646?

CVE-2025-67646 is a low-severity vulnerability in Telepedia TableProgressTracking, published on 10 Dec 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

TableProgressTracking is a MediaWiki extension to track progress against specific criterion. Versions 1.2.0 and below do not enforce CSRF token validation in the REST API. As a result, an attacker could craft a malicious webpage that, when visited by an authenticated user on a wiki with the extension enabled, would trigger unintended authenticated actions through the victim's browser. Due to the lack of token validation, an attacker can delete or track progress against tables. This issue is patched in version 1.2.1 of the extension.

Weakness: CWE-352 (Cross-Site Request Forgery)

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


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

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

## Is CVE-2025-67646 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-67646 is a low-severity vulnerability in Telepedia TableProgressTracking, published on 10 Dec 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-67646 in the wild and no public exploit code.

Affected product: Telepedia TableProgressTracking. 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-67646/ (Markdown: https://insights.sbomify.com/CVE-2025-67646/index.md)
```

## Sources

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

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