Stored XSS via unescaped project name
Published May 16, 2023 · Updated Jan 23, 2025
Stored XSS in Jenkins TestComplete support Plugin 2.8.1 and earlier allows remote authenticated users to execute script in a viewer's browser. The test result page inserts the configured TestComplete project name into rendered output without escaping it, preserving attacker-controlled markup for later viewing. Item/Configure permission is required to store the name, and exploitation occurs when another user opens the affected test result page.
Summary
What happened
Stored XSS in Jenkins TestComplete support Plugin 2.8.1 and earlier allows remote authenticated users to execute script in a viewer's browser. The test result page inserts the configured TestComplete project name into rendered output without escaping it, preserving attacker-controlled markup for later viewing. Item/Configure permission is required to store the name, and exploitation occurs when another user opens the affected test result page.
The record
- CVE
- CVE-2023-33002
- Published
- May 16, 2023
- Updated
- Jan 23, 2025
- Vendor
- Jenkins Project
- Product
- TestComplete support
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 16, 2023CVE publishedPublication date reported by the CVE source.
- Jan 23, 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=0 <=2.8.1
What conditions does exploitation require?
What is affected?
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