| CVE |
Vendors |
Products |
Updated |
CVSS v3.1 |
| The FV Player 8 plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'data.videos[].fv_wp_flowplayer_field_splash' parameter in all versions up to, and including, 8.1.9 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The wp_ajax_fv_player_db_save handler's ownership and capability check is conditional on the presence of the data.update field; omitting it bypasses authorization entirely, allowing a Subscriber-level attacker to overwrite any existing video record using an enumerable video ID — and the valid nonce required by the endpoint is issued to every logged-in visitor of any page hosting the publicly accessible [fvplayer_editor] shortcode. |
| In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 missing authorization allowed project viewers to remove VCS roots |
| In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the P4 Code Review build tab was possible |
| In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 an LDAP injection allowed bypassing login restrictions |
| In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 remote code execution was possible via a file write bypass in the Kotlin DSL sandbox |
| In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on build and queue pages was possible |
| In JetBrains TeamCity before 2026.2 two-factor authentication bypass was possible via access token management |
| In JetBrains TeamCity before 2026.2, 2026.1.4 stored XSS in the unified diff page syntax highlighting was possible |
| In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in SSH key management was possible |
| In JetBrains TeamCity before 2026.2, 2026.1.4 improper authorization allowed users with the Run build permission to delete Perforce workspaces |
| 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 reflected XSS on the notification rules page was possible |
| In JetBrains TeamCity before 2026.2, 2026.1.4 reflected XSS in build problem details was possible |
| In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 reflected XSS on the build feature parameters page was possible |
| In JetBrains TeamCity before 2026.2 privilege escalation of project-scoped access tokens via concurrent project deletion 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 arbitrary file write via read-write file channels in the Kotlin DSL sandbox was possible |
| In JetBrains TeamCity before 2026.2 improper authorization allowed project-limited access tokens to act with full permissions via XML-RPC |