XSS CVEs.
Published CVEs classified as xss, ranked by exploit odds.
-
CVE-2026-133055
In JetBrains TeamCity before 2026.2.1, 2026.1.5 stored XSS on the Failure Conditions page was possible
-
CVE-2026-133056
In JetBrains TeamCity before 2026.2.1, 2026.1.5 stored XSS in implicit agent requirements was possible
-
CVE-2026-133052
In JetBrains TeamCity before 2026.2.1, 2026.1.5 a DOM-based XSS in the plugin installation dialog was possible
-
CVE-2026-133054
In JetBrains TeamCity before 2026.2.1, 2026.1.5 stored XSS in the Create Project dialog was possible
-
CVE-2026-133050
In JetBrains TeamCity before 2026.2.1, 2026.1.5 stored and reflected XSS in Space project connection dialogs was possible
-
CVE-2026-133051
In JetBrains TeamCity before 2026.2.1, 2026.1.5 stored XSS in the JaCoCo coverage settings was possible
-
CVE-2026-133046
In JetBrains TeamCity before 2026.2.1 stored XSS in recipe export errors was possible
-
CVE-2026-133047
In JetBrains TeamCity before 2026.2.1, 2026.1.5 stored XSS on the thread dump page was possible
-
CVE-2026-133049
In JetBrains TeamCity before 2026.2.1 stored XSS in the Pull Requests health report for VCS roots was possible
-
CVE-2026-133039
In JetBrains TeamCity before 2026.2.1 stored XSS in the Pull Requests health report for Space connections was possible
-
CVE-2026-133041
In JetBrains TeamCity before 2026.2.1, 2026.1.5 stored XSS in the Commit Status Publisher settings was possible
-
CVE-2026-133036
In JetBrains TeamCity before 2026.2.1 stored XSS in the Issue Trackers health report was possible
-
CVE-2026-133037
In JetBrains TeamCity before 2026.2.1, 2026.1.5 stored XSS in the GitHub App repository selector was possible
-
CVE-2026-133038
In JetBrains TeamCity before 2026.2.1 stored XSS in the Maven Build Info project header was possible
-
CVE-2026-133033
In JetBrains TeamCity before 2026.2.1 stored XSS in Maven Build Info module links was possible
-
CVE-2026-133034
In JetBrains TeamCity before 2026.2.1 stored XSS on the Changes page was possible
-
CVE-2026-133035
In JetBrains TeamCity before 2026.2.1 stored XSS on the change Files tab was possible
-
CVE-2026-133031
In JetBrains TeamCity before 2026.2.1 stored XSS in Git VCS root settings was possible
-
CVE-2026-133032
In JetBrains TeamCity before 2026.2.1 reflected XSS on the Cloud Profiles page was possible
-
CVE-2026-123968
The Slimbox plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment (anchor title within comment HTML)' parameter in all versions up to, and including, 1.0.8 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. WordPress core comment KSES permits unauthenticated commenters to post anchor elements with href and title attributes, so an entity-encoded payload stored in the title attribute survives sanitization verbatim; the browser then decodes the entities when populating the DOM .title property, and the Slimbox library's jQuery .html() caption sink renders it as executable HTML.
-
CVE-2026-123971
The Slimbox Plugin plugin for WordPress is vulnerable to Stored DOM-Based Cross-Site Scripting via the 'el.title (HTML-decoded title attribute of a stored <a rel^=lightbox> element)' parameter in all versions up to, and including, 1.3 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. Exploitation requires a companion plugin such as bbPress that permits low-privileged users to store anchor elements with arbitrary title and rel attributes, as WordPress core comment handling does not preserve rel on anchor tags by default.
-
CVE-2026-123969
The Fancy Lightbox plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment' parameter in all versions up to, and including, 1.0.0 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 without administrator interaction requires that the attacker first have one comment approved so that a subsequent payload comment is auto-published; the injected script only executes when a user clicks the malicious image link inside the comment. Successful exploitation additionally requires an action by an administrator — the attacker cannot trigger the vulnerability on their own.
-
CVE-2026-85413
The Foxtool All-in-One: Contact chat button, Custom login, Media optimize images plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'foxtool_image_id' parameter in all versions up to, and including, 2.5.3 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. A subscriber-level attacker can store a payload in their own profile's foxtoolpic user-meta that executes in an administrator's browser session when the administrator views the user via the Users → Edit screen.
-
CVE-2026-123972
The WP-Slimbox2 Plugin plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment' parameter in all versions up to, and including, 1.1.3.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. Successful exploitation requires a logged-in user, typically an administrator, to click the attacker's image link in the comment; however, because unmoderated comments appear in the WordPress moderation queue where administrators routinely interact with them, the moderation gate does not meaningfully prevent exploitation. Successful exploitation causes the attacker's own account to receive the complete Administrator role.
-
CVE-2026-125061
The administration page "Offene Bestellungen" (open orders) of the JTL PayPal Checkout plugin for JTL-Shop outputs the customer name of pending orders without output encoding. A registered customer (free self-registration) can submit an HTML-entity-encoded name, which is decoded to markup when the billing address of an order is written. If the PayPal payment is left unfinished, the order is listed on the page and the name is rendered as markup in the browser of an administrator who opens the page. The script code runs with the privileges of that administrator and can, for example, create a new administrator account. Guest orders are not affected, because the name is encoded again.
-
CVE-2026-132990
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in Change Log revision tooltips was possible
-
CVE-2026-132991
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 reflected XSS on the Slack connection test page was possible
-
CVE-2026-132992
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the agent info popup was possible
-
CVE-2026-132993
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the notification rules editor was possible
-
CVE-2026-132995
In JetBrains TeamCity before 2026.2 stored XSS on the build step settings page was possible
-
CVE-2026-132989
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the SSH Keys page was possible
-
CVE-2026-132980
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the Schedule Trigger branch filter settings was possible
-
CVE-2026-132981
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the Versioned Settings page was possible
-
CVE-2026-132982
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the build Report Tab dialog was possible
-
CVE-2026-132983
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the Report Tabs settings page was possible
-
CVE-2026-132984
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the project Report Tab dialog was possible
-
CVE-2026-132971
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the Schedule Trigger dependency settings was possible
-
CVE-2026-132972
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the Slack Notifier settings page was possible
-
CVE-2026-132973
In JetBrains TeamCity before 2026.2, 2026.1.5 stored XSS on the external Kotlin DSL editor status page was possible
-
CVE-2026-132975
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in issue tracker links was possible
-
CVE-2026-132977
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the Agent Statistics tooltip was possible
-
CVE-2026-132979
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the checkout rules editor was possible
-
CVE-2026-132963
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the checkout rules path preview was possible
-
CVE-2026-132964
In JetBrains TeamCity before 2026.2 stored XSS on the Duplicates report tab was possible
-
CVE-2026-132965
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the unknown VCS root page was possible
-
CVE-2026-132966
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in build statistics charts was possible
-
CVE-2026-132967
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the build Issues tab was possible
-
CVE-2026-132968
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the Large Build Log health report was possible
-
CVE-2026-132970
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the Finish Build Trigger editor was possible
-
CVE-2026-132955
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the Pull Requests branch filter health report was possible
A list of CVEs whose flaw type is xss, sorted by how likely they are to be exploited (EPSS). Classification uses the CWE weakness id where present, and a small local model otherwise.