In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the checkout rules editor was possible
Search vulnerabilities
Stored Cross‑Site Scripting via Branch Filter in JetBrains TeamCity
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the Schedule Trigger branch filter settings was possible
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in Change Log revision tooltips was possible
Forminator Forms <= 1.58.4 - Unauthenticated Stored Cross-Site Scripting via Uploaded .rtx File
The Forminator Forms – Contact Form, Payment Form & Custom Form Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'upload-1 (the File Upload field's element_id)' parameter in all versions up to, and including, 1.58.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. This vulnerability is an incomplete fix for CVE-2024-1794; exploitation requires that the Forminator form's File Upload field is left at plugin defaults (no 'custom-files' restriction configured) and that the server maps no Content-Type to the .rtx extension — the default behavior of the Debian/Ubuntu Apache package used by the official WordPress Docker image and many shared hosts.
Forminator Forms <= 1.58.4 - Unauthenticated Stored Cross-Site Scripting via Rich-Text Textarea Save-and-Continue Draft
The Forminator Forms – Contact Form, Payment Form & Custom Form Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'textarea-N (rich-text draft value, saved as Save-and-Continue draft meta)' parameter in all versions up to, and including, 1.58.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. This requires the targeted form to have a Rich-Text Textarea field with Save-and-Continue enabled and public submission permissions — once a crafted draft is saved, the payload executes whenever any user, including an administrator, resumes the draft or opens the Draft ID link from the Forminator Submissions screen.
Stored XSS in JetBrains TeamCity NPM Registry Build Feature
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the NPM Registry build feature was possible
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the AWS Credentials build feature was possible
In JetBrains TeamCity before 2026.2, 2026.1.4 stored XSS in the Xcode runner SDK selection was possible
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the Pull Requests branch filter health report was possible
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the artifact dependency tree was possible
Stored XSS Vulnerability in JetBrains TeamCity Test Details Page
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the Test Details page was possible
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in build statistics charts was possible
Stored XSS in TeamCity Schedule Trigger Dependencies
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the Schedule Trigger dependency settings was possible
Stored XSS via Issue Tracker Links in JetBrains TeamCity
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in issue tracker links was possible
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the Agent Statistics tooltip was possible
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the Versioned Settings page was possible
In JetBrains TeamCity before 2026.2, 2026.1.4 reflected XSS in the build log tree view was possible
Photo Gallery, Sliders, Proofing and Themes <= 4.5.6 - Unauthenticated Stored Cross-Site Scripting via Comment Link via Thickbox Lightbox 'all_images' Context
The Photo Gallery, Sliders, Proofing and Themes – NextGEN Gallery plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment' parameter in all versions up to, and including, 4.5.6 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. This requires the site administrator to have configured the Thickbox lightbox effect with the "Try to apply to all images" context (thumbEffectContext=all_images), and exploitation additionally depends on an administrator approving the attacker's initial comment so that subsequent comments from that author are auto-approved.
Product Import Export for WooCommerce <= 2.6.9 - Unauthenticated Stored Cross-Site Scripting via Product Review Import Placeholder Re-expansion
The Product Import Export for WooCommerce – CSV Product Importer & Exporter plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'author (initial store via wp-comments-post.php) / CSV cell on import' parameter in all versions up to, and including, 2.6.9 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. The exploit requires an administrator to approve the attacker's review, then export and re-import it using the plugin's default column mapping, with the import taking the INSERT branch — which occurs automatically on any site whose database table prefix is not the literal 'wp_', when the CSV has no comment_ID mapping, or when the original review has been trashed. Successful exploitation additionally requires an action by an administrator — the attacker cannot trigger the vulnerability on their own.
ShortPixel Image Optimizer <= 6.6.1 - Unauthenticated Stored Cross-Site Scripting via Comment Content via CDN URL Rewriter
The ShortPixel Image Optimizer – Optimize Images, Convert WebP & AVIF plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment' parameter in all versions up to, and including, 6.6.1 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. Exploitation requires the administrator to have enabled the 'Deliver WebP/AVIF images using the ShortPixel CDN' (useCDN) option, after which any unauthenticated visitor can submit a comment containing a crafted url() payload inside an allowed HTML construct such as <acronym title="...">, which WordPress comment kses preserves on save; the dangerous attribute-boundary breakout occurs only at render time inside the ob_start output-buffer rewriter, where kses does not apply.