Export limit exceeded: 430483 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 430483 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 430483 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 430483 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (430483 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-120404 | 1 Apache | 1 Opennlp | 2026-11-21 | 6.4 Medium |
| The built-in regular expression name finder for latitude and longitude coordinates uses a pattern that is vulnerable to excessive backtracking. An attacker who can supply text that an application analyzes with this name finder can cause high CPU consumption, leading to denial of service. Users are recommended to upgrade to version 2.5.13 or 3.0.0, which fix the issue. | ||||
| CVE-2026-123971 | 2 Peppolone, Wordpress-extensions | 2 Slimbox Plugin, Slimbox Plugin | 2026-11-21 | 6.4 Medium |
| 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-125695 | 1 Wordpress-extensions | 1 Lightbox With Photoswipe | 2026-11-21 | 7.5 High |
| The Lightbox with PhotoSwipe WordPress plugin before 5.19.0 does not escape image link URLs before outputting them in the attributes of the lightbox share menu, allowing unauthenticated users to perform Stored Cross-Site Scripting attacks via comments when the PhotoSwipe 4 frontend is used. | ||||
| CVE-2026-125788 | 2 Wedevs, Wordpress-extensions | 2 Happy Addons For Elementor, Happy Addons For Elementor | 2026-11-21 | 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-125287 | 2 Wordpress-extensions, Wptasty | 2 Tasty Recipes Lite, Tasty Recipes Lite | 2026-11-21 | 5.3 Medium |
| Insertion of Sensitive Information Into Sent Data vulnerability in WPTasty Tasty Recipes Lite tasty-recipes-lite allows Retrieve Embedded Sensitive Data.This issue affects Tasty Recipes Lite: from n/a through 1.2.11. | ||||
| CVE-2026-126005 | 2 Foliovision, Wordpress-extensions | 2 Fv Flowplayer Video Player, Fv Flowplayer Video Player | 2026-11-21 | 6.4 Medium |
| The FV Flowplayer Video Player plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'data[videos][0][fv_wp_flowplayer_field_src]' parameter in all versions up to, and including, 7.5.57.7212 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 fv_player_db_save AJAX endpoint's INSERT path is gated only by a per-user preview nonce and never calls current_user_can(), allowing any authenticated subscriber-level user who possesses their own nonce to store the malicious payload. Exploitation by attackers with subscriber-level access and above requires that administrator has enabled the plugin option fvwpflowplayer['profile_videos_enable_bio']=true (off by default), which enqueues the shortcode editor and the per-user preview_nonce on wp-admin/profile.php for every logged-in user. On a default installation, where that is not configured, the vulnerability requires attackers with contributor-level access and above. | ||||
| CVE-2026-125085 | 2026-11-21 | 8.8 High | ||
| The Nexter Extension – Security, Performance, Code Snippets & Site Toolkit plugin for WordPress is vulnerable to Privilege Escalation in versions up to, and including, 4.9.0 This is due to the role_switcher_to_view_admin_as() function handling the `reset-view` branch without a capability check or nonce when the caller's own login is supplied, combined with an incomplete cleanup hook (maybe_prevent_switchback_to_administrator) that exits early when the user's current roles equal the stored view role and that is never triggered when WordPress core's WP_User::set_role() short-circuits because the account already has only the target role. This makes it possible for authenticated attackers, with subscriber-level access and above, to elevate their privileges to Administrator. | ||||
| CVE-2026-124769 | 1 Xone | 1 Xonemanager | 2026-11-21 | N/A |
| Authorization omission in the 'users' POST operation at '/xmanagercore/api/services/' in XOneManager 3.8.3.0. The API checks project membership but fails to validate the role required to manage users. An authenticated user can view the list of users in the project, including their internal IDs, first names, and last names. | ||||
| CVE-2026-124771 | 1 Xone | 1 Xonemanager | 2026-11-21 | N/A |
| Authorization omission in the 'admusers' operation of the POST request to '/xmanagercore/api/services/' in XOneManager 3.8.3.0. The API fails to verify the required role for querying the directory. An authenticated member of the project can obtain the list of platform accounts—including administrative accounts—along with details such as email addresses, roles, and associated companies. | ||||
| CVE-2026-124772 | 1 Xone | 1 Xonemanager | 2026-11-21 | N/A |
| Authorization bypass in the publication of XOneManager 3.8.3.0 updates. During testing, the server accepted initial requests from an authenticated project member with read-only access without verifying publication permissions. If the workflow is completed, updates with modified content could be distributed to managed devices. | ||||
| CVE-2026-125094 | 2 Optimole, Wordpress-extensions | 2 Optimole, Optimole | 2026-11-21 | 7.2 High |
| The Optimole – Optimize Images | Convert WebP & AVIF | CDN & Lazy Load | Image Optimization plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment' parameter in all versions up to, and including, 4.2.19 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 AMP plugin to be active in Transitional or Standard template mode, and comments must be open on the target post, which is the WordPress default. | ||||
| CVE-2026-126334 | 1 Phoenixframework | 1 Phoenix Live View | 2026-11-21 | N/A |
| Incorrect Authorization vulnerability in phoenixframework phoenix_live_view allows an authenticated user to mount a router-mounted LiveView without the on_mount hooks of its live_session via a phx_join message that carries neither a "url" nor a "redirect" key. The catch-all clause of the private Phoenix.LiveView.Channel.authorize_session/3 in lib/phoenix_live_view/channel.ex accepts a join without a URL for any session, including a root LiveView mounted at the router. The channel then mounts the LiveView with no route, and only a route adds the live_session hooks to the mount lifecycle. Checks that those hooks perform on the connected mount do not run, and event checks that they attach through attach_hook/4 are never attached. The attacker needs a valid session token for the LiveView, which only the HTTP render issues, after the hooks pass there. on_mount hooks declared in the LiveView module still run. This issue affects phoenix_live_view: from 0.16.0 before 1.0.20, from 1.1.0-rc.0 before 1.1.34, and from 1.2.0-rc.0 before 1.2.14. | ||||
| CVE-2026-126054 | 2026-11-21 | N/A | ||
| A Path Traversal vulnerability in workspace directory handling and Git integration in Google Cloud Dataform, BigQuery Studio and Colab Enterprise on Google Cloud Platform allows an authenticated remote attacker to read private files and create arbitrary files across tenant repositories using crafted workspace operations and Git integration requests. This vulnerability was patched on 10 October 2026, and no customer action is needed. | ||||
| CVE-2026-112115 | 1 Asus | 1 Armoury Crate | 2026-11-21 | N/A |
| An untrusted search path in ASUS Armoury Crate allows a local, low-privileged user to achieve privilege escalation by executing a crafted library at a high integrity level, via user-controlled environment settings inherited by an elevated process. Refer to the ' Security Update for Armoury Crate App ' section on the ASUS Security Advisory for more information. | ||||
| CVE-2026-121482 | 2 Openssl, Redhat | 2 Openssl, Hummingbird | 2026-11-21 | 7.5 High |
| Verifying a maliciously crafted CMS or PKCS#7 SignedData message with CRL checking enabled may consume excessive CPU time, growing with the square of the message size. | ||||
| CVE-2026-120753 | 1 Eclipse | 1 Eclipse Ditto | 2026-11-21 | N/A |
| In Eclipse Ditto versions 1.1.0 to 3.9.8, when pre-authentication is enabled, the gateway service accepts the pre-authenticated subject not only from the `x-ditto-pre-authenticated` HTTP header set by a trusted reverse proxy, but also from an undocumented `x-ditto-pre-authenticated` URL query parameter that a client can set. A reverse proxy that only overwrites the header therefore does not stop clients from supplying their own subject. With the default configuration of the Ditto Helm chart (`global.jwtOnly: false`, which implicitly enables pre-authentication), the bundled nginx skips HTTP Basic authentication for any request with an `Authorization: Bearer` header and forwards it without the pre-authentication header. An unauthenticated remote attacker can send an invalid Bearer token together with the query parameter to authenticate as any chosen policy subject. Pre-authentication succeeds before the JWT is validated, so the attacker can read and modify Things and Policies with that subject's permissions. As a mitigation, disable pre-authentication in the gateway (`ENABLE_PRE_AUTHENTICATION=false`) or, when using the Helm chart, configure `global.jwtOnly: true`. | ||||
| CVE-2026-120157 | 1 Dorsettcontrols | 1 Infoscan | 2026-11-21 | 5.3 Medium |
| The publicly distributed InfoScan Electron installer contains configuration files identifying hostnames associated with customer installations and internal development, testing, and database infrastructure. An individual who obtains and inspects the installer can extract these hostnames without authenticating to the affected systems. | ||||
| CVE-2026-120255 | 1 Dorsettcontrols | 1 Infoscan | 2026-11-21 | 4.3 Medium |
| InfoScan uses hard-coded cryptographic keys and initialization-vector values in its database-encryption implementation. The application uses these values to encrypt the MongoDB password before storing it in the Windows registry. Because the cryptographic material is embedded in the distributed application, an individual with access to the encrypted registry value and the application code may be able to recover the database password. | ||||
| CVE-2026-120271 | 1 Dorsettcontrols | 1 Infoscan | 2026-11-21 | 5.3 Medium |
| InfoScan contains an unauthenticated information disclosure vulnerability in its mobile-enumeration and version-reporting endpoints. A remote attacker can send HTTP requests without authentication to retrieve system configuration information, including usernames and display names, multifactor authentication configuration status, session settings, application version information, server details, hardware module firmware versions, and the BACnet/IP port used by the installation. | ||||
| CVE-2026-120298 | 1 Dorsettcontrols | 1 Infoscan | 2026-11-21 | 5.3 Medium |
| InfoScan fails to properly handle certain malformed or incomplete requests to its login and password-reset endpoints. These requests can trigger unhandled server exceptions that return detailed Node.js stack traces to the requester. The responses disclose internal filesystem paths, application directory names, source file locations, and line numbers. | ||||