Export limit exceeded: 419066 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (419066 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-120202 | 1 Highflame-ai | 1 Ramparts | 2026-11-03 | 6.5 Medium |
| Highflame ramparts 0.8.1 through 0.8.10 contains a security scan bypass vulnerability that allows attackers to hide malicious payloads because collect_bundle_siblings and walk_bundle_subdir skip nested directories and .pyc files. Attackers can distribute a skill bundle with an unchecked-hash .pyc under scripts/<subdir>/__pycache__/ that ramparts silently ignores, while CPython executes it when the skill runs. | ||||
| CVE-2026-120204 | 1 Deepseek-ai | 1 Deepinfer | 2026-11-03 | 5.6 Medium |
| DeepInfer through 0.1.0 contains a path traversal vulnerability in the unauthenticated /profile endpoint that allows remote attackers to create arbitrary directories via the output_dir parameter. Attackers, including cross-site GET requests from an operator's browser, can write chrome trace files to exhaust disk or inodes and use error messages as a filesystem oracle. | ||||
| CVE-2026-120206 | 1 Thelia | 4 Thelia, Thelia Back-office Default Template, Thelia Back-office Default Twig Template and 1 more | 2026-11-03 | 5.9 Medium |
| Thelia before 3.2.0 contains a cross-site request forgery vulnerability in the back office that allows attackers to forge administrative actions because per-session CSRF tokens leak via URL query strings. Attackers can reuse leaked tokens or target the unprotected setToggleVisibilityAction and updatePositionAction to make logged-in administrators delete, hide or reorder catalogue and configuration objects. | ||||
| CVE-2026-120207 | 1 Thelia | 1 Thelia Page Module | 2026-11-03 | 7.1 High |
| Thelia Page Module before 2.0.4 contains a cross-site request forgery vulnerability that allows remote attackers to delete page tags, documents and images by abusing back-office delete routes lacking CSRF tokens and permission checks. Attackers can lure a logged-in administrator into navigating to crafted GET requests that walk sequential ids, removing TheliaLibrary images, their files and variants across pages, products and categories. | ||||
| CVE-2026-118147 | 1 Microsoft | 5 Microsoft Visual Studio 2017 Version 15.9, Microsoft Visual Studio 2019 Version 16.11, Microsoft Visual Studio 2022 Version 17.14 and 2 more | 2026-11-03 | 7.4 High |
| Improper certificate validation in Visual Studio allows an unauthorized attacker to perform spoofing over a network. | ||||
| CVE-2026-115946 | 1 Perl | 1 Xs::libbrotli | 2026-11-03 | N/A |
| XS::libbrotli versions before 1.2.1.0 for Perl bundle a brotli library with an out-of-bounds write in the decoder. Affected versions compile a bundled brotli into static archives that dependent XS modules link against at build time, rather than using the system library. The bundled copy, 1.0.7 or 1.1.0 across the range, carries the decoder out-of-bounds write described in CVE-2026-111497. Version 1.2.1.0 updates it to brotli 1.2.1. XS::libbrotli has no Perl interface, so the decoder is reached through any dependent module that decompresses untrusted data with it. An attacker supplying a crafted brotli stream can corrupt decoder state, disclose memory, crash the process, or potentially execute arbitrary code. Upgrading the system brotli does not remediate this. | ||||
| CVE-2026-120248 | 1 Thelia | 2 Thelia, Thelia Back-office Default Twig Template | 2026-11-03 | 4.8 Medium |
| Thelia before 3.1.1 contains a stored cross-site scripting vulnerability that allows authenticated back-office administrators with store update permission to inject scripts by uploading unsanitized SVG logo_file or banner_file images. Attackers can upload an SVG with an onload payload served from /admin/store-media/logo or the public cache/images/store/ directory to execute scripts against visitors and higher-privileged administrators. | ||||
| CVE-2026-120249 | 1 Thelia | 1 Thelia Back-office Default Twig Template | 2026-11-03 | 6.5 Medium |
| Thelia Back-office Default Twig Template before 1.1.1 contains a cross-site request forgery vulnerability in the /admin/product/combinations/update and /admin/product/default-price/update routes, which accept GET requests without anti-CSRF token checks. Attackers can lure a logged-in administrator into following a crafted link to rewrite product combination prices, stock, weight, EAN and sale flags, zeroing omitted prices. | ||||
| CVE-2026-120250 | 1 Marketcalls | 1 Openalgo | 2026-11-03 | 5.3 Medium |
| OpenAlgo 1.0.0.29 before 2.0.3.1 contains an improper certificate validation vulnerability in utils/email_utils.py and utils/email_debug.py that disables TLS hostname and certificate checks for STARTTLS and SMTPS. Network-positioned attackers can present a forged certificate to intercept SMTP credentials and all later mail, including password-reset links. | ||||
| CVE-2026-120251 | 1 Cgohlke | 1 Imagecodecs | 2026-11-03 | 5.5 Medium |
| imagecodecs 2026.3.6 through 2026.10.10 contains an infinite loop vulnerability in ccitt_fax4_decode_size() that allows attackers to hang the calling process by supplying a crafted CCITT Group 4 stream. Attackers can provide an 8-byte G4 stream lacking EOFB to ccittfax4_decode() or the numcodecs Ccittfax4 codec, consuming full CPU until the process is killed. | ||||
| CVE-2026-120252 | 1 Cgohlke | 1 Imagecodecs | 2026-11-03 | 5.5 Medium |
| imagecodecs 2023.1.23 through 2026.10.10 contains a stack-based buffer overflow vulnerability in the lossless JPEG Define Huffman Table parser in decode_jpegsof3(). Attackers can supply a crafted lossless JPEG whose DHT symbol counts wrap an 8-bit sum, overflowing the 32-entry HufVal and HufSz stack arrays and crashing the calling process. | ||||
| CVE-2026-115205 | 1 Wordpress-extensions | 1 Azexo Store Locator | 2026-11-03 | N/A |
| The AZEXO Store Locator WordPress plugin through 1.4 does not have a capability check or any authorization control when deleting a post, allowing any authenticated user, such as a subscriber, to delete arbitrary posts and pages. | ||||
| CVE-2026-106004 | 1 Wordpress-extensions | 1 Dt Lms | 2026-11-03 | N/A |
| The DT LMS WordPress plugin through 1.2 does not perform capability or nonce checks on one of its AJAX actions, allowing unauthenticated attackers to revoke any learner's course and class completion status. | ||||
| CVE-2026-105967 | 2 Ghozylab, Wordpress-extensions | 2 Gallery For Social Photo, Gallery For Social Photo | 2026-11-03 | N/A |
| The Gallery for Social Photo WordPress plugin through 1.0.0.41 does not validate a user-supplied URL before using it to perform a server-side request, allowing unauthenticated attackers to make the server issue requests to arbitrary internal hosts and read the responses. | ||||
| CVE-2026-104647 | 1 Wordpress-extensions | 1 Wemail | 2026-11-03 | N/A |
| The weMail WordPress plugin through 2.1.6 does not correctly verify user capabilities in its REST API permission checks, treating any user whose role is in the weMail WordPress plugin through 2.1.6's allowed-roles list (Editor and above by default) as authorised for every action, which allows such users to perform administrator-level actions including enumerating all registered users with their email addresses and modifying the weMail WordPress plugin through 2.1.6's own access-control configuration. | ||||
| CVE-2026-91075 | 2 Eupago, Wordpress-extensions | 2 Eupago Gateway Woocommerce, Eupago Gateway For Woocommerce | 2026-11-03 | 5.3 Medium |
| The Eupago Gateway For Woocommerce WordPress plugin from 4.5.0 through 4.7.5 does not verify the authenticity of incoming payment-confirmation webhook requests in some configurations, allowing unauthenticated attackers to forge a payment confirmation and mark a pending order as paid without paying for it. | ||||
| CVE-2026-103327 | 1 Wordpress-extensions | 1 Cryptocloud | 2026-11-03 | 5.3 Medium |
| The CryptoCloud WordPress plugin from 3.0.0 through 3.0.1 does not verify the authenticity of the payment notifications received by its gateway callback, as the integrity check is skipped while the webhook secret is left at its empty default, allowing unauthenticated attackers to mark arbitrary orders as paid or failed without any payment being made. | ||||
| CVE-2026-103379 | 1 Wordpress-extensions | 1 Wati Chat And Notification | 2026-11-03 | N/A |
| The WATI Chat and Notification WordPress plugin through 1.1.8 does not require a valid, non-empty secret on a public endpoint that returns its stored API token, which an unauthenticated attacker can then present to a second public endpoint to obtain the order-received URL of any WooCommerce order and read the customer's name, address, phone number and email address. The endpoints are reachable in the WATI Chat and Notification WordPress plugin through 1.1.8's default state and are closed only once a WATI account is connected. | ||||
| CVE-2026-104648 | 1 Wordpress-extensions | 1 Wemail | 2026-11-03 | N/A |
| The weMail WordPress plugin through 2.1.6 does not restrict a site-wide third-party email-service API key to administrators, exposing it in an admin screen that users with the Editor role can reach by default, which allows them to obtain a reusable credential usable without a WordPress session to impersonate other users and sever the site's email-service connection. | ||||
| CVE-2026-105770 | 1 Octo-sts | 1 App | 2026-11-03 | 5.3 Medium |
| Octo STS (github.com/octo-sts/app) before 0.11.2 returns trust policy configuration to callers whose OIDC token does not satisfy that policy. TrustPolicy.CheckToken included the policy's issuer, subject and audience values or patterns and claim_pattern names and regular expressions in its PermissionDenied errors, which Exchange returned verbatim. Exchange also selected the GitHub App installation before checking the token, so errors from resolving the policy's app or app_pattern pin were returned to callers the policy does not trust. An attacker who holds any validly signed OIDC token, such as a GitHub Actions token from a repository they own, and who knows or guesses a target owner/repo and identity name can read that policy's matching rules, even when the policy is stored in a private repository. These rules often name internal repositories, branches, environments or cloud account identifiers. The issue does not allow minting tokens or bypassing a trust policy. This issue is fixed in 0.11.2. | ||||