Export limit exceeded: 430681 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 430681 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 430681 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 430681 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 430681 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 430681 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 430681 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (430681 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-122223 | 2 Wordpress-extensions, Wpbakery | 2 Wpbakery Page Builder, Wpbakery Page Builder | 2026-11-21 | 6.4 Medium |
| The plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'values[text_shadow_color]' parameter in all versions up to, and including, 9.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The wp_kses_post sanitization applied at save time does not strip the payload because it is stored as URL-encoded JSON inside a shortcode attribute, containing no literal HTML tags for kses to tokenize, leaving the malicious value intact until render time. | ||||
| CVE-2026-129344 | 1 Phoenixframework | 1 Phoenix | 2026-11-21 | N/A |
| Uncaught Exception vulnerability in phoenixframework phoenix allows an unauthenticated attacker to cause a denial of service via a client-selected legacy serializer on binary channel broadcasts. When an application broadcasts {:binary, data} payloads on a channel topic, any client that connects without a vsn parameter, or with vsn=1.0.0, and joins that topic makes those broadcasts fail. Phoenix.Channel.Server.send/4 encodes each broadcast with every subscriber's own serializer inside the PubSub dispatch loop, calling fastlane!/1 with no rescue, and the negotiated Phoenix.Socket.V1.JSONSerializer raises Protocol.UndefinedError on a binary payload. Every binary broadcast on the topic then crashes the broadcasting process and skips every subscriber dispatched after the attacker. For broadcasts arriving from other nodes the loop runs in the PubSub adapter worker, whose repeated crashes restart the PubSub supervisor and empty the node's subscription registry while sockets stay connected. This issue affects phoenix: from 1.5.7 before 1.5.16, from 1.6.0-rc.0 before 1.6.18, from 1.7.0-rc.0 before 1.7.25, and from 1.8.0-rc.0 before 1.8.17. | ||||
| CVE-2026-132967 | 1 Jetbrains | 1 Teamcity | 2026-11-21 | 6.8 Medium |
| In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the build Issues tab was possible | ||||
| CVE-2026-132968 | 1 Jetbrains | 1 Teamcity | 2026-11-21 | 5.4 Medium |
| 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-132969 | 1 Jetbrains | 1 Teamcity | 2026-11-21 | 6.8 Medium |
| In JetBrains TeamCity before 2026.2, 2026.1.4 stored XSS in the Xcode runner configuration selection was possible | ||||
| CVE-2026-132970 | 1 Jetbrains | 1 Teamcity | 2026-11-21 | 6.8 Medium |
| In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the Finish Build Trigger editor was possible | ||||
| CVE-2026-132972 | 1 Jetbrains | 1 Teamcity | 2026-11-21 | 4.8 Medium |
| 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 | 1 Jetbrains | 1 Teamcity | 2026-11-21 | 6.8 Medium |
| In JetBrains TeamCity before 2026.2, 2026.1.5 stored XSS on the external Kotlin DSL editor status page was possible | ||||
| CVE-2026-132974 | 1 Jetbrains | 1 Teamcity | 2026-11-21 | 6.8 Medium |
| In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the Promote build dialog for dependent builds was possible | ||||
| CVE-2026-132976 | 1 Jetbrains | 1 Teamcity | 2026-11-21 | 6.8 Medium |
| In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the Inspections (IntelliJ IDEA) build step editor was possible | ||||
| CVE-2026-132979 | 1 Jetbrains | 1 Teamcity | 2026-11-21 | 6.8 Medium |
| In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the checkout rules editor was possible | ||||
| CVE-2026-132980 | 1 Jetbrains | 1 Teamcity | 2026-11-21 | 6.8 Medium |
| 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-132990 | 1 Jetbrains | 1 Teamcity | 2026-11-21 | 3.1 Low |
| In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in Change Log revision tooltips was possible | ||||
| CVE-2026-132994 | 1 Jetbrains | 1 Teamcity | 2026-11-21 | 2.7 Low |
| In JetBrains TeamCity before 2026.2 the REST API exposed details of users not visible in the UI | ||||
| CVE-2026-133014 | 1 Jetbrains | 1 Teamcity | 2026-11-21 | 7.2 High |
| In JetBrains TeamCity before 2026.2.1, 2026.1.5 remote code execution was possible via public reflection in the Kotlin DSL sandbox | ||||
| CVE-2026-133016 | 1 Jetbrains | 1 Teamcity | 2026-11-21 | 8.8 High |
| In JetBrains TeamCity before 2026.2.1, 2026.1.5 remote code execution was possible via script definitions in the Kotlin DSL settings repository | ||||
| CVE-2026-133020 | 1 Jetbrains | 1 Teamcity | 2026-11-21 | 7.4 High |
| In JetBrains TeamCity before 2026.1.5 untrusted build approval for GitHub fork pull requests could be bypassed | ||||
| CVE-2026-133026 | 1 Jetbrains | 1 Teamcity | 2026-11-21 | 7.2 High |
| In JetBrains TeamCity before 2026.2.1, 2026.1.5 code injection in generated Kotlin DSL was possible via matrix build parameters | ||||
| CVE-2026-120676 | 2 Wordpress-extensions, Wpmudev | 2 Forminator Forms, Forminator Forms | 2026-11-21 | 7.2 High |
| 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. | ||||
| CVE-2026-119632 | 2 Wordpress-extensions, Wpmudev | 2 Forminator Forms, Forminator Forms | 2026-11-21 | 7.2 High |
| 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. | ||||