Stored script execution via GitHub Checks webhook
Published May 20, 2025 · Updated May 20, 2025
Stored XSS in the GitHub Checks Webhook in JetBrains TeamCity before 2025.03.2 allows remote authenticated users to run script in a viewer's browser. JetBrains identifies the GitHub Checks webhook as the input path but has not published which payload field is stored or which rendering path fails to encode it. Exploitation requires high-privilege access to supply webhook content and user interaction to view it; resulting script runs with TeamCity-origin permissions.
Summary
What happened
Stored XSS in the GitHub Checks Webhook in JetBrains TeamCity before 2025.03.2 allows remote authenticated users to run script in a viewer's browser. JetBrains identifies the GitHub Checks webhook as the input path but has not published which payload field is stored or which rendering path fails to encode it. Exploitation requires high-privilege access to supply webhook content and user interaction to view it; resulting script runs with TeamCity-origin permissions.
The record
- CVE
- CVE-2025-47851
- Published
- May 20, 2025
- Updated
- May 20, 2025
- Vendor
- JetBrains
- Product
- TeamCity
- Classifications
- CWE-79, T1203
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 20, 2025CVE publishedPublication date reported by the CVE source.
- May 20, 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 <2025.03.2
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