# CVE-2025-64760: Tuleap has missing CSRF protections in its tracker trigger management system

> Attackers can force users to create or remove tracker triggers in Tuleap due to missing CSRF protections, requiring an upgrade to fix.

- **Severity:** Medium 4.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:L`)
- **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:** 8 Dec 2025
- **Updated:** 9 Dec 2025
- **Also known as:** GHSA-f2xv-x3g6-4j9p

## What is CVE-2025-64760?

CVE-2025-64760 is a medium-severity vulnerability in Enalean Tuleap, published on 8 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

Tuleap is a free and open source suite for management of software development and collaboration. Versions of Tuleap Community Edition prior to 17.0.99.1763126988 and Tuleap Enterprise Edition prior to 17.0-3 and 16.13-8 have missing CSRF protections which allow attackers to create or remove tracker triggers. This issue is fixed in Tuleap Community Edition version 17.0.99.1763126988 and Tuleap Enterprise Edition versions 17.0-3 and 16.13-8.

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

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

It affects 1 product.


Products: Enalean Tuleap.

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

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

## Is CVE-2025-64760 being exploited?

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

## Other vulnerabilities in Enalean Tuleap

- [CVE-2018-17298](https://insights.sbomify.com/CVE-2018-17298/): Business logic in n/a (critical 9.8)
- [CVE-2018-7538](https://insights.sbomify.com/CVE-2018-7538/): SQL injection in n/a (critical 9.8)
- [CVE-2014-7178](https://insights.sbomify.com/CVE-2014-7178/): Command injection in n/a (critical 9.3)
- [CVE-2021-43806](https://insights.sbomify.com/CVE-2021-43806/): SQL injection in Tuleap (high 8.8)
- [CVE-2021-41154](https://insights.sbomify.com/CVE-2021-41154/): SQL injection in the "SVN core" commits browser (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-64760 is a medium-severity vulnerability in Enalean Tuleap, published on 8 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-64760 in the wild and no public exploit code.

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

## Sources

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

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