Tracker field modification via missing CSRF validation
Published Dec 8, 2025 · Updated Dec 9, 2025
CSRF in Tuleap before Community 17.0.99.1763803709 and Enterprise 16.13-9 or 17.0-4 allows remote authenticated users to modify tracker fields. The tracker field-dependency modification flow accepts state-changing requests without enforcing a CSRF token. A low-privileged account and victim interaction are required, and successful exploitation can alter tracker configuration and disrupt affected workflows.
Summary
What happened
CSRF in Tuleap before Community 17.0.99.1763803709 and Enterprise 16.13-9 or 17.0-4 allows remote authenticated users to modify tracker fields. The tracker field-dependency modification flow accepts state-changing requests without enforcing a CSRF token. A low-privileged account and victim interaction are required, and successful exploitation can alter tracker configuration and disrupt affected workflows.
The record
- CVE
- CVE-2025-65962
- 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.1763803709
- Affected versionversion=Tuleap Enterprise Edition < 16.13-9
- Affected versionversion=Tuleap Enterprise Edition < 17.0-4
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