Export limit exceeded: 430281 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 430281 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 430281 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 430281 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (430281 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-133259 | 1 Jetbrains | 1 Youtrack | 2026-11-21 | 4.3 Medium |
| In JetBrains YouTrack before 2026.2.19840 improper authorization allowed read-only users to change issue fields via agile boards | ||||
| CVE-2026-133262 | 1 Jetbrains | 1 Youtrack | 2026-11-21 | 5.4 Medium |
| In JetBrains YouTrack before 2026.2.19766 improper authorization allowed read-only users to change the visibility of restricted issues via agile boards | ||||
| CVE-2026-133263 | 1 Jetbrains | 1 Youtrack | 2026-11-21 | 3.7 Low |
| In JetBrains YouTrack before 2026.2.19840 missing authorization allowed guests to add issues to sprints | ||||
| CVE-2026-133303 | 1 Mitel | 1 Micollab | 2026-11-21 | 9 Critical |
| A vulnerability in the Audio, Web, and Video Conferencing (AWV) component of Mitel MiCollab through 10.3 (10.3.0.18) could allow an unauthenticated attacker to leverage pre-staged malicious content to conduct an XML injection attack due to insufficient parameter validation. A successful exploit could allow an attacker to execute arbitrary commands within the context of the system. This is MTLVULN-1862. | ||||
| CVE-2026-133323 | 1 Mitel | 1 Micollab | 2026-11-21 | 10 Critical |
| A vulnerability in the Audio, Web, and Video Conferencing (AWV) component of Mitel MiCollab through 10.3 (10.3.0.18) could allow an unauthenticated attacker to conduct a blind command injection attack due to insufficient parameter sanitization. A successful exploit could allow an attacker to execute arbitrary commands within the context of the system. This is MTLVULN-1864. | ||||
| CVE-2026-116619 | 2 Roxnor, Wordpress-extensions | 2 Metform – Contact Form, Survey, Quiz, Conditional Forms, Form Templates & Custom Form Builder For Elementor, Metform | 2026-11-21 | 7.2 High |
| The MetForm – Contact Form, Survey, Quiz, Conditional Forms, Form Templates & Custom Form Builder for Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'mf-te (the form-builder-chosen name of the Text Editor field)' parameter in all versions up to, and including, 4.3.3 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 published form containing a Text Editor block; the form's public markup exposes the submission nonce as data-form-nonce, allowing any unauthenticated visitor to satisfy the only submission barrier and store the malicious payload. | ||||
| CVE-2026-120119 | 2 Realmag777, Wordpress-extensions | 2 Husky, Husky | 2026-11-21 | 6.5 Medium |
| The HUSKY – Products Filter for WooCommerce Professional plugin for WordPress is vulnerable to time-based SQL Injection via the 'link (inner 'woof_text' query parameter)' parameter in all versions up to, and including, 1.4.7 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with subscriber-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. The exploit requires a valid product_messenger nonce, which is issued by the woof_redraw_woof AJAX endpoint to any visitor when the shortcode's by_only attribute is set — an attribute that can itself be forced via the attacker-controlled woof_shortcode request parameter, making the nonce trivially obtainable by any logged-in user. | ||||
| CVE-2026-116757 | 2 Themeum, Wordpress-extensions | 2 Tutor Lms, Tutor Lms | 2026-11-21 | 6.4 Medium |
| The Tutor LMS – eLearning and online course solution plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the '_tutor_profile_bio' parameter in all versions up to, and including, 4.2.0 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 injected anchor payload uses a full-viewport invisible overlay (position:fixed; width:100vw; height:100vh; opacity:0) so that any click on the public profile page triggers the tutor-copy-text handler, which passes a browser-decoded data-text value to tutor_toast() where it is parsed as live HTML by jQuery. | ||||
| CVE-2026-120526 | 2 Wclovers, Wordpress-extensions | 2 Wcfm Membership, Wcfm Membership | 2026-11-21 | 7.2 High |
| The WCFM Membership – WooCommerce Memberships for Multivendor Marketplace plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'wcfm_membership_registration_form[store_name]' parameter in all versions up to, and including, 2.12.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. The nonce required to reach the registration endpoint is publicly emitted on the /vendor-register/ page, making the endpoint fully reachable by unauthenticated attackers without any prior authentication or privilege escalation. | ||||
| CVE-2026-131609 | 2 Vendidero, Wordpress-extensions | 2 Germanized For Woocommerce, Germanized For Woocommerce | 2026-11-21 | 7.2 High |
| The Germanized for WooCommerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'billing_address.first_name (Store API checkout) → stored on parent order; withdrawal get_first_name() fallback' parameter in all versions up to, and including, 4.1.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. The payload is planted via an unauthenticated guest checkout order's billing first name through the WooCommerce Store API, with execution triggered by a subsequent unauthenticated withdrawal request submission whose nonce is publicly available on the /withdraw-from-contract/ page. | ||||
| CVE-2026-109196 | 2026-11-21 | 6.4 Medium | ||
| 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. | ||||
| CVE-2026-119177 | 2026-11-21 | 5.4 Medium | ||
| The Real Cookie Banner: GDPR & ePrivacy Cookie Consent plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment' parameter in all versions up to, and including, 5.4.2 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 that the cookie banner has been activated by the site administrator (the plugin's primary onboarding step) and that at least one prior comment from the same name and email identity has already been approved, after which WordPress core's comment_previously_approved default auto-approves subsequent comments without administrator action. | ||||
| CVE-2026-124216 | 2026-11-21 | 7.2 High | ||
| The Orphans plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment' parameter in all versions up to, and including, 3.4.5 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 a two-step comment chain: a benign first comment must be approved under a given name and email so that WordPress's comment_previously_approved mechanism auto-publishes the attacker's payload comment without moderation. | ||||
| CVE-2026-130323 | 2026-11-21 | 7.2 High | ||
| The Accept Stripe Payments plugin for WordPress is vulnerable to Stored DOM-Based Cross-Site Scripting via the 'href of any <a> element containing 'asp_action=show_pp&product_id='' parameter in all versions up to, and including, 2.1.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. Successful exploitation requires that a user clicks the attacker-placed comment link to trigger the sink; however, if the non-default 'Prefetch Payment Popup Scripts' option is enabled, execution occurs on page load with no user interaction required. | ||||
| CVE-2026-119157 | 2026-11-21 | 6.4 Medium | ||
| The PublishPress Capabilities: User Role Access Control, Admin Area Permissions plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'page_elements' parameter in all versions up to, and including, 2.53.0 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. Successful exploitation requires an administrator to open a Profile Features capture window and save at least one of the attacker-supplied rows on the Profile Features screen, which represents the ordinary documented use of the feature and leaves no visible indication to the administrator that malicious data was submitted. | ||||
| CVE-2026-124248 | 2026-11-21 | 5.4 Medium | ||
| The GPTranslate – Multilingual AI Translation Agent for WordPress: Translate Your Site with AI plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment' parameter in all versions up to, and including, 2.34.17 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 plugin's non-default 'HTML DOM method' to be enabled for server-side translation, and a translation row for the target language-prefixed URL must exist to arm the output buffer that routes page content through the vulnerable Simple HTML DOM parser. | ||||
| CVE-2026-116518 | 2026-11-21 | 7.2 High | ||
| The ElasticPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'orderby' parameter in all versions up to, and including, 5.3.5 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 injected payload is stored in the ep_query_log transient for up to 24 hours after a single unauthenticated frontend GET request, and only fires when an administrator subsequently opens the Status Report page and expands the Failed Queries panel. | ||||
| CVE-2026-107771 | 2026-11-21 | 5.4 Medium | ||
| The Speed Booster Pack ⚡ PageSpeed Optimization Suite plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'author' parameter in all versions up to, and including, 4.5.9.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 that the plugin's Lazy load media option is enabled and that the attacker's comment is approved by a site administrator or via auto-approval. | ||||
| CVE-2026-107654 | 2026-11-21 | 7.5 High | ||
| The One to one user Chat by WPGuppy plugin for WordPress is vulnerable to generic SQL Injection via the 'userId' parameter in all versions up to, and including, 1.1.6 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. The plugin's permission callback is trivially bypassed because it validates a JWT that the plugin itself signs using an attacker-supplied value from the guppy_guest_account cookie, and the guest code path (userType=0) skips the get_userdata() check that would confirm the userId corresponds to a real WordPress user. | ||||
| CVE-2026-123970 | 2026-11-21 | 6.4 Medium | ||
| The wpForo Forum plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'thread[body]' parameter in all versions up to, and including, 3.2.4 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. Successful execution of the injected script is limited to viewers whose forum access profile denies attachment viewing (va=0 or caa=0), meaning exploitation depends on an administrator having configured a custom forum access profile that permits reading but denies attachment viewing — this is not the default shipped configuration. | ||||