Remote Code Execution via Malicious Mercurial Repository Content in JetBrains TeamCity
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 remote code execution was possible via Mercurial repository contents
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 remote code execution was possible via Mercurial repository contents
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 remote code execution was possible via build access codes disclosed to project users
In JetBrains TeamCity before 2026.2 missing authorization allowed reading Qodana reports of other projects
In JetBrains TeamCity before 2026.2 stored XSS in the duplicate remote parameter health report was possible
In JetBrains TeamCity before 2026.2, 2026.1.4 the Perforce Administrator Access password could be written to the server log
In JetBrains TeamCity before 2026.2, 2026.1.4 stored XSS in Perforce job details was possible
In JetBrains TeamCity before 2026.2, 2026.1.4 authentication bypass via polling agent name rebinding was possible
In JetBrains TeamCity before 2026.2, 2026.1.4 improper authorization allowed project agent administrators to manage agents of other projects
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the queued build Overview tab was possible
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the configuration health popup was possible
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the artifact dependency tree was possible
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the diff view page was possible
In JetBrains TeamCity before 2026.2.2, 2026.1.6 remote code execution was possible via security context spoofing in the Kotlin DSL sandbox
In JetBrains TeamCity before 2026.2.2, 2026.1.6 remote code execution was possible via Maven dependencies of Kotlin DSL settings
MsgPack and NNTP protocol dissector crashes in 4.6.0 to 4.6.9 and 4.4.0 to 4.4.19 allows denial of service
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in WPKoi WordPress Themes WPKoi Templates for Elementor wpkoi-templates-for-elementor allows Stored XSS.This issue affects WPKoi Templates for Elementor: from n/a through 3.7.5.
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in weDevs Happy Addons for Elementor happy-elementor-addons allows Stored XSS.This issue affects Happy Addons for Elementor: from n/a through 3.51.3.
pretix offloads certain processes to background tasks that are run by a different server to avoid HTTP workers being clogged with processes that take longer than a usual web request. The browser periodically polls the server to see if the task is already finished using a UUID-shaped task ID. Once the task is completed, pretix resumes to the next step of the operation based on the result of the task. The system does however not check if the result stems from the correct type of task. Therefore, an attacker can supply the UUID of a task of a different type and pretix will continue with the result from the wrong task. In most cases, this will just result in an error because the return types do not match up, but in some cases this can be abused to extract objects the attacker usually should not see. Specifically, a vector was discovered that allowed to abuse this for unauthorized access to other people's ticket purchases. The attacker can, however, not control which purchases they get access to.
When configuring a device to use the security profile "pretixSCAN (kiosk mode, no order sync, no search)", the API search endpoint introduced in pretix 4.12 was not blocked correctly. This theoretically allows these devices to perform searches for orders even if that was not intended. If the device is in kiosk mode, the search button will still be hidden from users.
Our payment integration with Stripe did not properly validate payment status responses. An attacker could use a successful payment status response from one payment and supply it to the system for a different payment, gaining access to multiple valid tickets with only one payment. However, the attack requires knowledge of a valid charge ID from the same event which we believe is usually not exposed to users. To simplify attack surface, the fix removes support for incoming webhooks regarding payments created through Stripe's old "source" API. pretix stopped creating payments using this API in 2024.1 for most payment methods and in 2024.9 for all payment methods.