CVE-2025-27099 json
Tuleap allows XSS via the tracker names used in the semantic timeframe deletion message
published 2025-03-03 20 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-6011
- cvss
- 4.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 22%
- public exploits
- 0
- none known
Summary
Tuleap is an Open Source Suite to improve management of software developments and collaboration. Tuleap allows cross-site scripting (XSS) via the tracker names used in the semantic timeframe deletion message. A tracker administrator with a semantic timeframe used by other trackers could use this vulnerability to force other tracker administrators to execute uncontrolled code. This vulnerability is fixed in Tuleap Community Edition 16.4.99.1740067916 and Tuleap Enterprise Edition 16.4-5 and 16.3-10.
Patch / fix
- enalean tuleap 16.3-10, 16.4-5, 16.4.99.1740067916
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 20 mo ago
Exploit prediction
0.30% chance of exploitation in the next 30 days, higher than 22% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- tuleap.net https://tuleap.net/plugins/tracker/?aid=41858 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.8 | CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:N/I:L/A:L |
| NVD | 3.1 | 4.8 | CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N |
Affected products
- Enalean tuleap
Classification
References
-
github.com
/Enalean/tuleap/commit/bec10bd5c98f6570a2857f55e9656eec4b211e6c
patch
-
github.com
/Enalean/tuleap/security/advisories/GHSA-vqfj-2gqp-g89x
patch, vendor-advisory
-
tuleap.net
/plugins/tracker/?aid=41858
exploit, issue-tracking, vendor-advisory
Sources
- CVE List CVE-2025-27099
- NVD CVE-2025-27099
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.