In JetBrains TeamCity before 2026.2.1 missing authorization allowed running modified build steps via pipeline debug runs
Search vulnerabilities
Stored XSS in JetBrains TeamCity Maven Build Info Links
In JetBrains TeamCity before 2026.2.1 stored XSS in Maven Build Info module links was possible
In JetBrains TeamCity before 2026.2.2, 2026.1.6 reflected XSS on the Edit VCS Root page was possible
Accept Stripe Payments <= 2.1.4 - Unauthenticated Stored DOM-Based Cross-Site Scripting via Comment Link href Attribute
The Accept Stripe Payments plugin for WordPress is vulnerable to Stored DOM-Based Cross-Site Scripting via the 'href of any <a> element containing 'asp_action=show_pp&product_id='' parameter in all versions up to, and including, 2.1.4 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Successful exploitation requires that a user clicks the attacker-placed comment link to trigger the sink; however, if the non-default 'Prefetch Payment Popup Scripts' option is enabled, execution occurs on page load with no user interaction required.
In JetBrains TeamCity before 2026.2 password parameters containing a caret were not masked in build logs on Windows
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 the Cloud Profiles page disclosed cloud profiles of projects the user could not access
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the agent info popup was possible
Stored XSS via Notification Rules Editor in JetBrains TeamCity
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the notification rules editor was possible
In JetBrains TeamCity before 2026.2 stored XSS on the build step settings page was possible
In JetBrains TeamCity before 2026.2 mute and unmute operations via XML-RPC could be attributed to other users
In JetBrains TeamCity before 2026.2.1, 2026.1.5 remote code execution was possible via boot classpath libraries in the Kotlin DSL sandbox
In JetBrains TeamCity before 2026.2.1, 2026.1.5 remote code execution was possible via Git VCS root settings
In JetBrains TeamCity before 2026.2.1, 2026.1.5 remote code execution was possible via a UI patches callback in the Kotlin DSL sandbox
In JetBrains TeamCity before 2026.2.1, 2026.1.5 remote code execution was possible via a context parameters callback in the Kotlin DSL sandbox
In JetBrains TeamCity before 2026.2.1, 2026.1.5 remote code execution was possible via Mercurial subrepository paths
In JetBrains TeamCity before 2026.2.1 remote code execution was possible via the Notification Rules form
In JetBrains TeamCity before 2026.2.1 the build parameter editor allowed project settings viewers to recover protected credentials
In JetBrains TeamCity before 2026.2.1 stored XSS in Git VCS root settings was possible
In JetBrains TeamCity before 2026.2.1 reflected XSS on the Cloud Profiles page was possible
In JetBrains TeamCity before 2026.2.1 stored XSS on the Changes page was possible