Tracker trigger creation and deletion via CSRF
Published Dec 8, 2025 · Updated Dec 9, 2025
CSRF in Tuleap Community before 17.0.99.1763126988 and Enterprise before 17.0-3 or 16.13-8 allows attackers to create or remove tracker triggers. The tracker trigger creation and deletion handlers accept state-changing requests without validating a CSRF token. Exploitation requires a signed-in user with trigger-management access to load attacker-controlled content, allowing unauthorized changes to tracker automation.
Summary
What happened
CSRF in Tuleap Community before 17.0.99.1763126988 and Enterprise before 17.0-3 or 16.13-8 allows attackers to create or remove tracker triggers. The tracker trigger creation and deletion handlers accept state-changing requests without validating a CSRF token. Exploitation requires a signed-in user with trigger-management access to load attacker-controlled content, allowing unauthorized changes to tracker automation.
The record
- CVE
- CVE-2025-64760
- Published
- Dec 8, 2025
- Updated
- Dec 9, 2025
- Vendor
- Enalean
- Product
- Tuleap
- Classifications
- CWE-352
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 8, 2025CVE publishedPublication date reported by the CVE source.
- Dec 9, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Tuleap Community Edition < 17.0.99.1763126988
- Affected versionversion=Tuleap Enterprise Edition < 16.13-8
- Affected versionversion=Tuleap Enterprise Edition < 17.0-3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo