Export limit exceeded: 428387 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 428387 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 428387 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (428387 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-110009 | 2 Unzerplugins, Wordpress-extensions | 2 Unzer Payments, Unzer Payments | 2026-11-18 | 9.8 Critical |
| The Unzer Payments plugin for WordPress is vulnerable to Authentication Bypass leading to Account Takeover in all versions up to, and including, 2.2.1. The vulnerability exists because the Google Pay Express Checkout endpoint (`/?wc-api=google_pay_express`), handled by `startCheckoutDataWithNormalizedCustomerData`, accepts an attacker-controlled `paymentData.email` value and passes it to `createOrGetGuestCustomer()`, which resolves the submitted email to any existing WordPress user via `get_user_by('email', ...)` and then calls `wp_set_current_user()` and `wp_set_auth_cookie()` for the resolved user ID without verifying ownership of the email address, a password, a nonce, an authentication token, or any proof of payment from the payment provider. This makes it possible for unauthenticated attackers to log in as any existing WordPress user — including administrators — by submitting that user's known email address, receiving valid `wordpress_logged_in_*` session cookies for the targeted account and achieving full site takeover. The endpoint is entirely unprotected with no capability check, nonce validation, or payment-provider signature verification applied, and administrator email addresses are frequently discoverable via the WordPress REST API user enumeration endpoint (`/wp-json/wp/v2/users`), author archive pages, Gravatar lookups, or site contact footers. | ||||
| CVE-2024-58401 | 1 Webkul | 1 Bagisto | 2026-11-18 | 6.1 Medium |
| Bagisto 2.1.0 before 2.2.1 contains a client-side template injection vulnerability in the search page where the 'query' parameter is rendered unescaped inside a Vue app root. Unauthenticated attackers can send crafted VueJS template expressions to the /bagisto-common/search endpoint via the 'query' parameter to execute arbitrary JavaScript in victims' browsers. Exploitation evidence was first observed by the Shadowserver Foundation on 2024-07-30. | ||||
| CVE-2023-54422 | 1 Idocv | 1 Idocview | 2026-11-18 | 9.8 Critical |
| iDocView before 13.10.1_20231115 contains an unrestricted file upload vulnerability in the /html/2word endpoint that allows unauthenticated attackers to write arbitrary files by supplying a malicious url parameter. Attackers can send a crafted GET request with the url parameter to download linked resources with an unsanitized path and unblocked .jsp extension, achieving remote code execution. Exploitation evidence was first observed by the Shadowserver Foundation on 2023-11-22. | ||||
| CVE-2026-111518 | 1 Dell | 1 Alienware Command Center | 2026-11-18 | 3.1 Low |
| Dell Alienware Command Center (AWCC), versions prior to 6.14.105.0, contain an Improper Restriction of Rendered UI Layers or Frames vulnerability. A high privileged attacker with remote access could potentially exploit this vulnerability, leading to Denial of Service and Launch of Phishing Attacks. | ||||
| CVE-2026-111515 | 1 Dell | 1 Alienware Command Center | 2026-11-18 | 7.1 High |
| Dell Alienware Command Center (AWCC), versions prior to 6.14.105.0, contain an Improper Authorization in Handler for Custom URL Scheme vulnerability. An unauthenticated attacker with remote access could potentially exploit this vulnerability, leading to Command Execution and Launch of Phishing Attacks. | ||||
| CVE-2026-111514 | 1 Dell | 1 Alienware Command Center | 2026-11-18 | 7.3 High |
| Dell Alienware Command Center (AWCC), versions prior to 6.14.105.0, contain an Incorrect Default Permissions vulnerability. A low privileged attacker with local access could potentially exploit this vulnerability, leading to Arbitrary Code Execution and Elevation of Privilege. | ||||
| CVE-2026-111513 | 1 Dell | 1 Alienware Command Center | 2026-11-18 | 7.3 High |
| Dell Alienware Command Center (AWCC), versions prior to 6.14.105.0, contain an Improper Verification of Cryptographic Signature vulnerability. A low privileged attacker with local access could potentially exploit this vulnerability, leading to Arbitrary Code Execution and Elevation of Privilege. | ||||
| CVE-2026-114585 | 1 Ibm | 1 Engineering Ai Hub | 2026-11-18 | 7.6 High |
| IBM Engineering AI Hub 1.0.0 through 1.4.0 could allow a remote authenticated attacker to obtain sensitive information due to a server-side request forgery. | ||||
| CVE-2026-110521 | 1 Ibm | 1 Engineering Ai Hub | 2026-11-18 | 6.1 Medium |
| IBM Engineering AI Hub 1.0.0 through 1.4.0 is vulnerable to cross-site scripting. This vulnerability allows an unauthenticated attacker to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session. | ||||
| CVE-2026-115241 | 1 Wordpress-extensions | 1 Wpvivid Backup & Migration | 2026-11-18 | 6.5 Medium |
| The WPvivid — Backup, Migration & Staging WordPress plugin before 0.9.137 does not verify that a submitted snapshot identifier names a snapshot it actually created before using it as a database table-name prefix, so an authenticated administrator can supply the site's table prefix, or any other string, and cause the WPvivid — Backup, Migration & Staging WordPress plugin before 0.9.137 to drop every matching table, including the core WordPress tables, destroying the site's database. | ||||
| CVE-2026-115242 | 1 Wordpress-extensions | 1 Wpvivid Backup & Migration | 2026-11-18 | 5.5 Medium |
| The WPvivid — Backup, Migration & Staging WordPress plugin before 0.9.137 does not sanitize the staging destination folder supplied to its staging-start handler, applying only a generic text filter while the sibling writability-check handler applies the correct filename sanitizer, so an authenticated administrator can supply a path containing traversal sequences and make the WPvivid — Backup, Migration & Staging WordPress plugin before 0.9.137 write the copied site files outside the WordPress installation directory. | ||||
| CVE-2026-115243 | 1 Wordpress-extensions | 1 Wpvivid Backup & Migration | 2026-11-18 | 6.7 Medium |
| The WPvivid — Backup, Migration & Staging WordPress plugin before 0.9.137 does not validate the extension of the file it actually stores when handling an import upload: it checks the extension of a separate request field while saving the uploaded file itself with WordPress's upload type-checking disabled, so an authenticated administrator can store a file with an arbitrary extension, including a PHP file, in the WPvivid — Backup, Migration & Staging WordPress plugin before 0.9.137's import directory. This is an incomplete fix of CVE-2025-5961, whose extension check was applied to the wrong value. | ||||
| CVE-2026-115426 | 1 Wordpress-extensions | 1 Wpvivid Backup & Migration | 2026-11-18 | 5.5 Medium |
| The WPvivid — Backup, Migration & Staging WordPress plugin before 0.9.138 does not properly validate a backup storage directory path before using it to create directories and write files, allowing administrators to cause those directories and files to be created outside the intended backup location via path traversal. | ||||
| CVE-2026-132143 | 1 Draytek | 2 Vigor2960, Vigor2960 Firmware | 2026-11-18 | 9.9 Critical |
| A vulnerability has been found in DrayTek Vigor2960 up to 1.5.1.6. This vulnerability affects the function doWebBackup of the file /cgi-bin/mainfunction.cgi of the component Backup Handler. Such manipulation of the argument path/value leads to stack-based buffer overflow. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 1.5.1.7 is able to resolve this issue. The affected component should be upgraded. The vendor recommends: "1.5.1.6 isn't the latest version of 2960, the latest version fixes many security issues. And we have another one in our release plan which should solve the issues reported." | ||||
| CVE-2026-129993 | 1 Dokploy | 1 Dokploy | 2026-11-18 | 6.5 Medium |
| Dokploy is a free, self-hostable Platform as a Service (PaaS). Prior to 0.31.1, the settings.getWebServerSettings protected procedure returns the complete global web-server settings object to any authenticated member, including the stored sshPrivateKey, even though settings.saveSSHPrivateKey requires an administrator. A default member can therefore retrieve infrastructure, deployment, or server-management credentials that only an administrator can configure. This issue is fixed in version 0.31.1. | ||||
| CVE-2026-129987 | 1 Dokploy | 1 Dokploy | 2026-11-18 | 9.9 Critical |
| Dokploy is a free, self-hostable Platform as a Service (PaaS). Prior to 0.31.1, the database password validation used by the MySQL, PostgreSQL, MariaDB, MongoDB, and Redis change-password procedures permits backticks, and the procedures interpolate attacker-controlled passwords into Bash command strings. An authenticated user who can update a database password can trigger command substitution before the database command runs, resulting in arbitrary operating-system command execution with the Dokploy process privileges, which are typically root. This issue is fixed in version 0.31.1. | ||||
| CVE-2026-129991 | 1 Dokploy | 1 Dokploy | 2026-11-18 | 9.9 Critical |
| Dokploy is a free, self-hostable Platform as a Service (PaaS). Prior to 0.31.1, the backup prefix field is only checked for a nonempty value, and normalizeS3Path preserves shell metacharacters before the prefix is interpolated into rclone upload and retention-cleanup command strings. An authenticated organization member with backup permission for a service can execute arbitrary commands as root on the Dokploy host or configured remote server when a PostgreSQL, MySQL, MariaDB, MongoDB, libSQL, Compose, or web-server backup runs manually, on schedule, or performs retention cleanup. This issue is fixed in version 0.31.1. | ||||
| CVE-2026-129985 | 1 Dokploy | 1 Dokploy | 2026-11-18 | N/A |
| Dokploy is a free, self-hostable Platform as a Service (PaaS). Prior to 0.31.1, a user-controlled schedule appName is joined into the schedule directory path and interpolated without shell quoting into commands that create the directory and write the schedule script. An authenticated user who can create or update a dokploy-server schedule can inject operating-system commands that execute with the Dokploy process privileges when the schedule is saved, including root privileges on typical installations. This issue is fixed in version 0.31.1. | ||||
| CVE-2026-129316 | 1 Dokploy | 1 Dokploy | 2026-11-18 | 9.9 Critical |
| Dokploy is a free, self-hostable Platform as a Service (PaaS). From 0.29.13 until 0.31.0, the Docker terminal, container-log, and monitoring WebSocket handlers accept a caller-controlled serviceId as authorization but do not consistently bind the requested containerId or appName to that service. A member with read access to any service can consequently target unrelated containers, obtain a root shell in the Dokploy panel container, read other tenants' logs and statistics, and use the mounted Docker socket to compromise the host. This issue is fixed in version 0.31.0. | ||||
| CVE-2026-129986 | 1 Dokploy | 1 Dokploy | 2026-11-18 | 9.9 Critical |
| Dokploy is a free, self-hostable Platform as a Service (PaaS). Prior to 0.31.1, mount.deleteFileMount passes a path containing the user-controlled filePath to the local removeFileOrDirectory helper, which interpolates it unquoted into rm -rf, while the remote branch is quoted. An authenticated member with file-mount create and delete permissions can execute arbitrary commands in the host context immediately when deleting a local file mount, without requiring a running container. This issue is fixed in version 0.31.1. | ||||