Stored XSS via unsanitized child submitter names
Published Jul 29, 2025 · Updated Jul 29, 2025
Stored XSS in affected Tuleap Community and Enterprise editions allows remote authenticated users to execute script in victims' browsers. The artifact-link field renders a parent artifact's child list without sanitizing the child submitter's real name, so an attacker-controlled image error handler becomes executable markup. Exploitation requires control of an artifact in a tracker without the unified artifact-link field and a victim who opens the children list; the script then runs in that victim's Tuleap session.
Summary
What happened
Stored XSS in affected Tuleap Community and Enterprise editions allows remote authenticated users to execute script in victims' browsers. The artifact-link field renders a parent artifact's child list without sanitizing the child submitter's real name, so an attacker-controlled image error handler becomes executable markup. Exploitation requires control of an artifact in a tracker without the unified artifact-link field and a victim who opens the children list; the script then runs in that victim's Tuleap session.
The record
- CVE
- CVE-2025-53541
- Published
- Jul 29, 2025
- Updated
- Jul 29, 2025
- Vendor
- Enalean
- Product
- Tuleap
- Classifications
- CWE-79, T1203
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 29, 2025CVE publishedPublication date reported by the CVE source.
- Jul 29, 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 < 16.9.99.1751892857
- Affected versionversion=Tuleap Enterprise Edition < 16.8-5
- Affected versionversion=Tuleap Enterprise Edition >= 16.9, < 16.9-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
- Vendor reproduction steps for stored artifact-list XSSproof of concept · demonstrated
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