OAuth login impact via cross-site request forgery
Published Jul 28, 2025 · Updated Jul 28, 2025
Cross-site request forgery in JetBrains TeamCity before 2025.07 allows remote authenticated users to cause unspecified OAuth login impact. JetBrains identifies the locus as the external OAuth login integration but has not published the affected endpoint, request flow, or missing CSRF validation. Exploitation requires authenticated access, high-complexity conditions, and victim interaction; the vendor assessment limits consequences to confidentiality and integrity.
Summary
What happened
Cross-site request forgery in JetBrains TeamCity before 2025.07 allows remote authenticated users to cause unspecified OAuth login impact. JetBrains identifies the locus as the external OAuth login integration but has not published the affected endpoint, request flow, or missing CSRF validation. Exploitation requires authenticated access, high-complexity conditions, and victim interaction; the vendor assessment limits consequences to confidentiality and integrity.
The record
- CVE
- CVE-2025-54529
- Published
- Jul 28, 2025
- Updated
- Jul 28, 2025
- Vendor
- JetBrains
- Product
- TeamCity
- Classifications
- CWE-352
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 28, 2025CVE publishedPublication date reported by the CVE source.
- Jul 28, 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.07
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