# CVE-2025-66906: Cross-site request forgery in n/a

> Attackers can exploit CSRF in Turms Admin API to gain escalated privileges, requiring administrators to upgrade to a patched version.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 19 Dec 2025
- **Updated:** 19 Dec 2025
- **Also known as:** GHSA-6jch-g84g-hpwx

## What is CVE-2025-66906?

CVE-2025-66906 is a medium-severity vulnerability in n/a, published on 19 Dec 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Cross Site Request Forgery (CSRF) vulnerability in Turms Admin API thru v0.10.0-SNAPSHOT allows attackers to gain escalated privileges.

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

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

It affects 1 product.


Products: Turms-Im Turms.

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

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

## Is CVE-2025-66906 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-66906 exists.

## Other vulnerabilities in n/a

- [CVE-2025-66909](https://insights.sbomify.com/CVE-2025-66909/): Denial of service in n/a (high 7.5)
- [CVE-2025-66911](https://insights.sbomify.com/CVE-2025-66911/): Missing authorization in n/a (medium 6.5)
- [CVE-2025-66910](https://insights.sbomify.com/CVE-2025-66910/): Information disclosure in n/a (medium 6.0)
- [CVE-2025-66908](https://insights.sbomify.com/CVE-2025-66908/): File upload in n/a (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-66906 is a medium-severity vulnerability in n/a, published on 19 Dec 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-66906 exists.

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

## Sources

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

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