Export limit exceeded: 430090 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (430090 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-124213 | 2026-11-20 | N/A | ||
| ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2026-125822. Reason: This candidate is a reservation duplicate of CVE-2026-125822. Notes: All CVE users should reference CVE-2026-125822 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage. | ||||
| CVE-2026-125788 | 2 Wedevs, Wordpress-extensions | 2 Happy Addons For Elementor, Happy Addons For Elementor | 2026-11-20 | 5.3 Medium |
| Missing Authorization vulnerability in weDevs Happy Addons for Elementor happy-elementor-addons allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Happy Addons for Elementor: from n/a through 3.51.3. | ||||
| CVE-2026-129043 | 2 Tribulant, Wordpress-extensions | 2 Newsletters, Newsletters | 2026-11-20 | 9.3 Critical |
| Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Tribulant Software Newsletters newsletters-lite allows SQL Injection.This issue affects Newsletters: from n/a through 4.18.2. | ||||
| CVE-2026-129063 | 2 Brainstormforce, Wordpress-extensions | 2 Spectra, Spectra | 2026-11-20 | 7.1 High |
| Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Brainstorm Force Spectra ultimate-addons-for-gutenberg allows Stored XSS.This issue affects Spectra: from n/a through 2.20.5. | ||||
| CVE-2026-79790 | 2026-11-20 | N/A | ||
| This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | ||||
| CVE-2026-99799 | 1 Linux | 2 Linux, Linux Kernel | 2026-11-20 | N/A |
| In the Linux kernel, the following vulnerability has been resolved: io_uring/sqpoll: don't wait for the thread to exit io_sq_thread_stop() wakes the SQPOLL thread and waits for it to exit. The thread belongs to the thread group that created the ring, so a SIGSTOP or the cgroup freezer holds it in get_signal(), and the wake up doesn't change that. io_ring_exit_work() then sleeps in that wait until someone continues or kills the process. iou_exit has 64 slots, so 64 closed SQPOLL rings of a stopped process keep every other ring from being freed, for everyone. Don't wait. Set the stop bit, wake the thread, and let it exit when it gets to run again. The sqd can now outlive its last ring, so give it a second refcount with one reference for the rings and one for the thread, and free it with the last one. The thread can't reach a freed ring, rings leave ctx_list before dropping their reference, and the io-wq hash is refcounted. | ||||
| CVE-2026-99800 | 1 Linux | 2 Linux, Linux Kernel | 2026-11-20 | N/A |
| In the Linux kernel, the following vulnerability has been resolved: io_uring: free the task context after a grace period A task other than the owner can free a request, io_ring_exit_work() running the local task_work of a DEFER_TASKRUN ring for example, or io_do_iopoll() reaping completions. io_put_task() then takes the else branch: percpu_counter_sub(&tctx->inflight, 1); if (unlikely(atomic_read(&tctx->in_cancel))) wake_up(&tctx->wait); put_task_struct(tctx->task); The first line is what lets the owner leave io_uring_cancel_generic(), and on exec it frees the tctx right after. Nothing holds that off for the remaining three lines, the task reference only covers a tctx freed along with the task_struct. It used to work out because io_uring_del_tctx_node() took the uring_lock that the freeing side holds across io_put_task(), until that moved to tctx_lock. Free the tctx with kfree_rcu(), and enter an RCU read section in io_put_task() before the count is dropped. | ||||
| CVE-2026-121714 | 1 Rabbitmq | 1 Rabbitmq-server | 2026-11-20 | N/A |
| RabbitMQ is a messaging and streaming broker. In the affected revision identified by the advisory, the AMQP 1.0 server_mode parser in deps/amqp10_common/src/amqp10_binary_parser.erl stops at the first body section and preserves the remaining bytes in bare_and_footer without validating message-section order. An authenticated publisher with write permission can place a properties section carrying a forged user-id after the body, causing rabbit_access_control:check_user_id/2 to see no user-id while permissive downstream AMQP 1.0 decoders or AMQP 0-9-1 conversion through classic and quorum queues expose the forged identity. Applications that rely on RabbitMQ-validated user-id metadata can therefore accept attacker-controlled publisher attribution. Strict consumers that reject out-of-order sections are not vulnerable to identity spoofing, and the issue does not bypass broker routing or destination authorization. This issue is fixed in version 4.3.5. | ||||
| CVE-2026-129998 | 1 1panel | 1 Maxkb | 2026-11-20 | 7.3 High |
| MaxKB is an open-source AI assistant for enterprise. Prior to 2.10.7-lts, custom Tool Init Param definitions accept attacker-controlled props_info.rules[].validator strings through POST /admin/api/workspace/{workspace_id}/tool and PUT /admin/api/workspace/{workspace_id}/tool/{tool_id}, store them without restriction, and pass them to eval() when the parameter form renders. An authenticated user with the default USER workspace role can store JavaScript and trigger execution by opening the tool's Debug screen before entering or submitting a parameter value. The same Init Param form is exposed to accounts with edit permission on the tool, but execution by a different account was not independently verified. The confirmed script runs in the MaxKB origin; access to another user's bearer token and authenticated account authority is plausible only if that user renders the malicious form. This issue is fixed in version 2.10.7-lts. | ||||
| CVE-2026-133693 | 2 Continue, Continuedev | 2 Continue, Continue | 2026-11-20 | 3.3 Low |
| A weakness has been identified in continuedev continue 2.0.0/2.1.0. Affected is the function validateSearchAndReplaceFilepath of the file gui/src/util/clientTools/editImpl.ts of the component Edit Tool. Executing a manipulation can lead to path traversal. The attack requires local access. The vendor was contacted early about this disclosure but did not respond in any way. | ||||
| CVE-2026-133937 | 1 Highlight | 1 Highlight.js | 2026-11-20 | 5.3 Medium |
| A flaw has been found in highlight highlight.js up to 11.12.0. The affected element is the function hljs.highlight of the file src/languages/livescript.js of the component Language Grammar Handler. Executing a manipulation of the argument text can lead to inefficient regular expression complexity. The attack can be launched remotely. The exploit has been published and may be used. The pull request to fix this issue awaits acceptance. | ||||
| CVE-2026-133561 | 1 Mattermost | 1 Mattermost | 2026-11-20 | 4.3 Medium |
| Mattermost versions 11.2.x <= 11.2.4 fail to validate that the redirect target on the web app landing page that prompts users to open links in the desktop app stays on the Mattermost origin which allows an unauthenticated attacker to redirect a user to an arbitrary external site via a crafted link. Mattermost Advisory ID: MMSA-2026-00893 | ||||
| CVE-2026-131763 | 2 Nsquared, Wordpress-extensions | 2 Simply Schedule Appointments, Simply Schedule Appointments | 2026-11-20 | 5.4 Medium |
| Missing Authorization vulnerability in NSquared Simply Schedule Appointments simply-schedule-appointments allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Simply Schedule Appointments: from n/a through 1.6.13.6. | ||||
| CVE-2026-129185 | 2 Payplus, Wordpress-extensions | 2 Payplus Payment Gateway, Payplus Payment Gateway | 2026-11-20 | 4.3 Medium |
| The PayPlus Payment Gateway plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 8.3.4 This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with subscriber-level access and above, to generate PayPlus payment page links for arbitrary WooCommerce orders belonging to any customer, overwrite those orders' payment method and PayPlus-related order meta, and trigger PayPlus API calls using the store's credentials — including, when a POS EMV device is configured, initiating a charge request to the store's physical POS terminal. The exploit requires no nonce and no special capability beyond being logged in, as the authorization block is unreachable on the AJAX path due to the inverted isset() predicate. | ||||
| CVE-2026-131709 | 2 Wordpress-extensions, Wpmet | 2 Shopengine, Shopengine | 2026-11-20 | 6.5 Medium |
| Missing Authorization vulnerability in Wpmet ShopEngine shopengine allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects ShopEngine: from n/a through 4.9.9. | ||||
| CVE-2026-128113 | 2026-11-20 | N/A | ||
| ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. Reason: This candidate was issued in error. Notes: All references and descriptions in this candidate have been removed to prevent accidental usage. | ||||
| CVE-2026-99404 | 1 Linux | 2 Linux, Linux Kernel | 2026-11-20 | N/A |
| In the Linux kernel, the following vulnerability has been resolved: xfs: check fork type against dabtree block magic number LOLLM complains that we fail to flag dabtree blocks that should never be associated with the file fork -- data forks can't point to xattr leaves, and attr forks can't point to dirent blocks. Add the missing checks. | ||||
| CVE-2026-120508 | 2 Smub, Wordpress-extensions | 2 Charitable – Donation & Fundraising Platform (donation Forms, Recurring Donations & Fundraising Campaigns), Charitable | 2026-11-20 | 7.2 High |
| The Charitable – Donation & Fundraising Platform (Donation Forms, Recurring Donations & Fundraising Campaigns) plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'stripe_payment_method' parameter in all versions up to, and including, 1.8.15.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. The nonce required to reach the nopriv AJAX endpoint is publicly obtainable from any rendered campaign donation form, making exploitation trivially accessible to unauthenticated visitors on sites with Stripe configured as a payment gateway. | ||||
| CVE-2026-130601 | 2 Bdthemes, Wordpress-extensions | 2 Element Pack Elementor Addons, Element Pack Elementor Addons | 2026-11-20 | 7.1 High |
| Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in BdThemes Element Pack Elementor Addons bdthemes-element-pack-lite allows Stored XSS.This issue affects Element Pack Elementor Addons: from n/a through 10.0.9. | ||||
| CVE-2026-134136 | 2026-11-20 | 4.8 Medium | ||
| OceanWP WordPress Theme before 4.2.9 contains a stored cross-site scripting vulnerability in the oceanwp_edd_terms_list() function in inc/edd/edd-helpers.php, which allows authenticated users with EDD download category creation permissions to inject malicious JavaScript by crafting a category name that breaks out of an unescaped HTML title attribute. Attackers can create a category name containing an event-handler payload that executes in the browser of visitors who interact with the category link on the public EDD archive page, potentially compromising an administrator's session if they view the affected page while authenticated. | ||||