Export limit exceeded: 430287 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (430287 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-129935 | 1 Mongodb | 1 Go Driver | 2026-11-21 | 3.7 Low |
| The MongoDB Go Driver does not neutralize NUL characters in the user name and password values it places into the message it builds for SASL PLAIN authentication. A party who can choose the login values that an application passes to the driver can alter where the fields of that message begin and end. This may result in a receiving system reading a login name and secret that differ from the values the application supplied. Authenticating as a different account still requires that account's password. Only deployments that use SASL PLAIN authentication are affected. | ||||
| CVE-2026-130236 | 1 Okta | 1 Auth0 Authorization Extension | 2026-11-21 | 8.5 High |
| In the Auth0 Authorization Extension, request authentication handling can process claims from query parameters independently of header validation. Under specific preconditions, this may allow an authenticated tenant user to issue requests to the extension's administrative endpoints. Also, input handling during rule generation may permit modification of the tenant login rule published by the extension. | ||||
| CVE-2026-133958 | 1 Redhat | 1 Quay | 2026-11-21 | 5.5 Medium |
| A flaw was found in Quay. Insufficient validation of repository notification webhook URLs allows an authenticated administrator to trigger Server-Side Request Forgery (SSRF). By specifying an internal URL or a redirect to an internal destination, an attacker can force the Quay worker to issue unauthorized HTTP requests to internal network locations and cloud metadata services. | ||||
| CVE-2026-131239 | 1 Splunk | 1 Enterprise Security | 2026-11-21 | 7.3 High |
| In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the run_collect capability could store attacker-controlled values in Updates data. If another user who can access the System Update Status report selects an affected row, Splunk Enterprise Security could run attacker-controlled Search Processing Language (SPL) commands using the permissions of the user who selects the row. The user who stores the values could then access sensitive data and modify data available to the user who selects the row. The vulnerability is possible because the System Update Status report does not validate destination, signature, and vendor-product values before inserting them into drilldown searches. For more information see Define roles on the Splunk platform with capabilities (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/manage-splunk-platform-users-and-roles/define-roles-on-the-splunk-platform-with-capabilities) and System Update Status (https://help.splunk.com/en/splunk-enterprise-security-8/splunk-app-for-pci-compliance/installation-and-configuration-manual/8.7/configure-reports/system-update-status) in the Splunk documentation. | ||||
| CVE-2026-131209 | 1 Splunk | 1 Enterprise Security | 2026-11-21 | 8.3 High |
| In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the ueba_ers_execution_post capability could cause the User and Entity Behavior Analytics (UEBA) Content App to run arbitrary Search Processing Language (SPL) commands with elevated permissions through an Entity Risk Score calculation. With this access, the user could expose stored credentials and other data outside the permissions assigned to that role. The vulnerability is possible because the UEBA Content App does not validate Entity Risk Score calculation values before including them in SPL searches. For more information see Installing the UEBA Content App for Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/administer/8.5/user-and-entity-behavior-analytics/installing-the-ueba-content-app-for-splunk-enterprise-security), Entity risk scoring in Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/administer/8.4/risk-based-alerting/entity-risk-scoring-in-splunk-enterprise-security), and Roles and knowledge objects in UEBA for Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/administer/8.8/user-and-entity-behavior-analytics/ueba-content-app-for-on-premises/roles-and-knowledge-objects-in-ueba-for-splunk-enterprise-security) in the Splunk documentation. | ||||
| CVE-2026-131202 | 1 Splunk | 1 Enterprise Security | 2026-11-21 | 9.1 Critical |
| In Splunk Enterprise Security versions below 8.7.0, a user who holds the "ess_admin" Splunk Enterprise Security role could execute arbitrary code on the search head as the user account running Splunk Enterprise by combining lookup file upload and Configuration Checker functionality. The vulnerability is possible because Splunk Enterprise Security does not restrict lookup upload file types or keep Configuration Checker module paths within the intended directory. For more information see Users and roles for Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/install/8.7/installation/users-and-roles-for-splunk-enterprise-security) and Create and manage lookups in Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/administer/8.7/managing-security-content/create-and-manage-lookups-in-splunk-enterprise-security) in the Splunk documentation. | ||||
| CVE-2026-131199 | 1 Splunk | 1 Enterprise Security | 2026-11-21 | 8.8 High |
| In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the mc_investigation_read capability could cause the Risk Event Timeline Representational State Transfer (REST) API to run arbitrary Search Processing Language (SPL) commands with elevated permissions. With this access, the user could expose stored credentials and modify indexes and lookup data available to those permissions. The vulnerability is possible because the affected REST API does not validate request values before including them in search macro arguments. For more information see Capability reference for Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/install/8.7/installation/capability-reference-for-splunk-enterprise-security) and Risk analysis (https://help.splunk.com/en/splunk-enterprise-security-8/user-guide/8.7/analytics/risk-analysis) in the Splunk documentation. | ||||
| CVE-2026-129409 | 1 Vi-solutions | 1 Visforms Extension For Joomla | 2026-11-21 | N/A |
| Joomla Extension - vi-solutions - Open redirects in data view controller and after form submission in Visforms extension 1.0.0-5.6.4, 6.0.0-6.2.1 - Return and redirect URLs taken from user input in the data/PDF controller and after a successful form submission were not validated, allowing redirects to external sites. | ||||
| CVE-2026-129413 | 1 Vi-solutions | 1 Visforms Extension For Joomla | 2026-11-21 | N/A |
| Joomla Extension - vi-solutions - IDOR in backend data export in Visforms extension 1.0.0-5.6.4, 6.0.0-6.2.1 - The backend export did not correctly verify permissions for the exported form, allowing backend users to export data of forms they are not authorized to access. | ||||
| CVE-2026-129402 | 1 Vi-solutions | 1 Visforms Extension For Joomla | 2026-11-21 | N/A |
| Joomla Extension - vi-solutions - Unauthenticated SQL injection in reload task in Visforms extension 1.0.0-5.6.4, 6.0.0-6.2.1 - Input placeholders in SQL field statements were inserted without quoting in the public reload task, allowing unauthenticated SQL injection in read queries. | ||||
| CVE-2026-129401 | 1 Vi-solutions | 1 Visforms Extension For Joomla | 2026-11-21 | N/A |
| Joomla Extension - vi-solutions - Open redirect on invalid form submission in Visforms extension 1.0.0-5.6.3, 6.0.0-6.2.0 - The return parameter of an invalid form submission was not validated, allowing redirects to external sites. | ||||
| CVE-2026-129397 | 1 Vi-solutions | 1 Visforms Extension For Joomla | 2026-11-21 | N/A |
| Joomla Extension - vi-solutions - Arbitrary file deletion via path traversal in CSS editor in Visforms extension 1.0.0-5.6.3, 6.0.0-6.2.0 - The delete and rename tasks of the CSS editor lacked authorization checks, CSRF protection and path validation, allowing backend users to delete files outside the CSS directory. | ||||
| CVE-2026-129396 | 1 Vi-solutions | 1 Visforms Extension For Joomla | 2026-11-21 | N/A |
| Joomla Extension - vi-solutions - Arbitrary file write leading to remote code execution in CSS editor in Visforms extension 1.0.0-5.6.3, 6.0.0-6.2.0 - The CSS editor did not restrict file names, extensions and paths of created and saved files, allowing privileged backend users to write arbitrary PHP files. | ||||
| CVE-2026-129416 | 1 Vi-solutions | 1 Visforms Extension For Joomla | 2026-11-21 | N/A |
| Joomla Extension - vi-solutions - Access restriction bypass for form submissions in Visforms extension 1.0.0-5.6.4, 6.0.0-6.2.1 - Form submissions did not check the access level of the form, allowing guests to submit forms restricted to specific user groups. | ||||
| CVE-2026-129404 | 1 Vi-solutions | 1 Visforms Extension For Joomla | 2026-11-21 | N/A |
| Joomla Extension - vi-solutions - Missing SQL statement permission check in form import and field creation in Visforms extension 1.0.0-5.6.4, 6.0.0-6.2.1 - The core.create.sql.statement permission was not enforced when importing forms or creating new fields, allowing backend users without this permission to store arbitrary SQL statements. | ||||
| CVE-2026-129234 | 1 Nltk | 1 Nltk | 2026-11-21 | 7.3 High |
| NLTK (Natural Language Toolkit) is a suite of open source Python modules, data sets, and tutorials supporting research and development in Natural Language Processing. Prior to 3.10.4, Prover9Parent.config_prover9 and Mace accept a relative binary_location and pass it to find_binary as path_to_bin, disabling the bare-name absolute-path guard. A local attacker who can plant prover9 or mace4 in the resolved working directory can cause subprocess.Popen to execute that binary with the invoking user's privileges. This issue is fixed in version 3.10.4. | ||||
| CVE-2026-19793 | 2 Vjinfotech, Wordpress-extensions | 2 Wp Import Export Lite, Wp Import Export Lite | 2026-11-21 | 8.8 High |
| The WP Import Export Lite plugin for WordPress is vulnerable to Limited Code Injection in all versions up to, and including, 3.9.32 via the 'comment' parameter. This is due to a two-stage shortcode check that evaluates the raw mapping placeholder before data substitution, causing the neutralizer to be skipped when attacker-controlled comment content containing a malicious [wpie_function] shortcode is substituted at runtime. This makes it possible for unauthenticated attackers to inject arbitrary PHP callables on the server. Exploitation requires an Administrator to perform the standard Export With Settings For Import followed by a New Import migration workflow, which is a routine operational task; the attacker themselves requires no account or authentication, needing only the ability to submit a pending comment on any comments-open post. | ||||
| CVE-2026-129406 | 1 Vi-solutions | 1 Visforms Extension For Joomla | 2026-11-21 | N/A |
| Joomla Extension - vi-solutions - Verification mail rate limit reset in Visforms extension 1.0.0-5.6.4, 6.0.0-6.2.1 - The rate limit for verification mails was reset on every form render, rendering the limit ineffective. | ||||
| CVE-2026-129407 | 1 Vi-solutions | 1 Visforms Extension For Joomla | 2026-11-21 | N/A |
| Joomla Extension - vi-solutions - Missing authorization and CSRF checks in reset and check-in tasks in Visforms extension 1.0.0-5.6.4, 6.0.0-6.2.1 - The tasks to reset submitted data and to check in forms lacked authorization checks and CSRF protection. | ||||
| CVE-2026-129923 | 1 Mongodb | 1 Rust Driver | 2026-11-21 | 3.7 Low |
| The MongoDB Rust Driver does not neutralize NUL characters in the user name and password values it places into the message it builds for SASL PLAIN authentication. A party who can choose the login values that an application passes to the driver can alter where the fields of that message begin and end. This may result in a receiving system reading a login name and secret that differ from the values the application supplied. Authenticating as a different account still requires that account's password. Only deployments that use SASL PLAIN authentication are affected. | ||||