# CVE-2025-64482: Tuleap missing CSRF protections in the File Release System

> Attackers can trick users into modifying SVN repository commit rules or immutable tags due to missing CSRF protections in the File Release System.

- **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:** 12 Nov 2025
- **Updated:** 13 Nov 2025
- **Also known as:** GHSA-w7h4-9vf6-q7rc

## What is CVE-2025-64482?

CVE-2025-64482 is a medium-severity vulnerability in Enalean tuleap, published on 12 Nov 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 an Open Source Suite to improve management of software developments and collaboration. Tuleap Community Edition prior to version 16.13.99.1762267347 and Tuleap Enterprise Edition prior to versions 17.01-, 16.13-6, and 16.12-9 don't have cross-site request forgery protections in the file release system. An attacker could use this vulnerability to trick victims into changing the commit rules or immutable tags of a SVN repo. Tuleap Community Edition 16.13.99.1762267347, Tuleap Enterprise Edition 17.0-1, Tuleap Enterprise Edition 16.13-6, and Tuleap Enterprise Edition 16.12-9 fix the issue.

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

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


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

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

## Is CVE-2025-64482 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-64482 is a medium-severity vulnerability in Enalean tuleap, published on 12 Nov 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-64482 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-64482/ (Markdown: https://insights.sbomify.com/CVE-2025-64482/index.md)
```

## Sources

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

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