Export limit exceeded: 390121 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (390121 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-87814 | 2 B3log, Siyuan | 2 Siyuan, Siyuan | 2026-09-10 | 7.3 High |
| SiYuan before v3.8.2 contains a stored cross-site scripting vulnerability in the search asset preview feature that fails to escape indexed asset content before inserting it into the DOM using innerHTML. Attackers who can place crafted text assets in a workspace can execute JavaScript in the SiYuan origin when victims preview the assets, enabling authenticated API requests and workspace manipulation. | ||||
| CVE-2026-82530 | 2 Ip2location, Wordpress | 2 Country Blocker, Wordpress | 2026-09-10 | 5.3 Medium |
| IP2Location Country Blocker plugin for WordPress before 2.45.0 contains an access control bypass vulnerability that allows unauthenticated remote attackers to circumvent IP-based restrictions by forging the X-Real-IP HTTP header. Attackers can set the X-Real-IP header to an allowlisted IP address to bypass page, link, or site-wide access restrictions and access otherwise-blocked resources. | ||||
| CVE-2026-47156 | 1 Mantisbt | 1 Mantisbt | 2026-09-10 | N/A |
| MantisBT is an open source bug tracker. Versions 2.28.3 and earlier contain a critical authentication bypass in the SOAP API's mci_check_login() function. Any user knowing any valid cookie_string can authenticate as any other user (knowing their username), including the administrator, without knowing the target's password. The vulnerability is exploitable with zero prior access on default MantisBT installations because self-registration is enabled by default ($g_allow_signup = ON). A self-registered user can use their own cookie_string (readable from their browser's MANTIS_STRING_COOKIE cookie after login) to impersonate the administrator via the SOAP API. The REST API is NOT affected. The REST API's AuthMiddleware derives the username server-side from the API token or session cookie, so the username cannot be spoofed. The Web UI is NOT affected. The Web UI authenticates via PHP session cookies (PHPSESSID) and validates the MANTIS_STRING_COOKIE against the logged-in user through auth_is_cookie_valid(). The username is derived server-side from the cookie, not supplied by the client. Version 2.28.4 contains a patch. No known workarounds are available. | ||||
| CVE-2026-89054 | 2026-09-10 | 8.2 High | ||
| A missing authorization vulnerability in OpenNMS Horizon allows configuration changes without authentication. The Spring Security policy for the /api/v2 REST API defines authorization rules for every HTTP method except PATCH, so the shipped @PATCH configuration endpoints for event configuration and SNMP data collection (which enable and disable event definitions and data-collection sources) are reachable with no authorization enforced. An unauthenticated attacker able to reach the web UI can disable event definitions and SNMP data collection, suppressing event and alarm generation and stopping metric collection - silently degrading monitoring and detection - with the change persisted and reloaded into the running system. The solution is to upgrade to Horizon 36.0.4 or newer. Meridian and Horizon installation instructions state that they are intended for installation within an organization's private networks and should not be directly accessible from the Internet. | ||||
| CVE-2026-87933 | 1 Davegamble | 1 Cjson | 2026-09-10 | 7.3 High |
| A vulnerability was found in DaveGamble cJSON up to 1.7.19. The affected element is the function cJSONUtils_MergePatch of the file cJSON_Utils.c. The manipulation results in use after free. The attack may be launched remotely. The exploit has been made public and could be used. The pull request to fix this issue awaits acceptance. | ||||
| CVE-2026-87561 | 1 Google | 1 Chrome | 2026-09-10 | 4.3 Medium |
| Incorrect authorization in Web Authentication in Google Chrome prior to 153.0.8010.36 allowed a remote attacker to bypass web origin policy via a crafted Chrome extension. (Chromium security severity: Low) | ||||
| CVE-2026-87543 | 1 Google | 1 Chrome | 2026-09-10 | 4.3 Medium |
| Missing authorization in Core in Google Chrome prior to 153.0.8010.36 allowed a remote attacker who had compromised the renderer process to bypass site isolation via a crafted HTML page. (Chromium security severity: Low) | ||||
| CVE-2026-87431 | 1 Google | 1 Chrome | 2026-09-10 | 7.5 High |
| Missing authorization in Extensions in Google Chrome prior to 153.0.8010.36 allowed a remote attacker to obtain sensitive information via a crafted Chrome extension. (Chromium security severity: Medium) | ||||
| CVE-2026-87429 | 1 Google | 1 Chrome | 2026-09-10 | 6.5 Medium |
| Missing authorization in ServiceWorker in Google Chrome prior to 153.0.8010.36 allowed a remote attacker who had compromised the renderer process to bypass system access restrictions via a crafted HTML page. (Chromium security severity: Low) | ||||
| CVE-2026-28624 | 1 Google | 1 Android | 2026-09-10 | 7.8 High |
| In multiple locations, there is a possible read/write access to files without the proper permissions due to a confused deputy. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation. | ||||
| CVE-2026-14892 | 1 Tanium | 1 Tanium Server | 2026-09-10 | 4.3 Medium |
| Tanium addressed an improper access controls vulnerability in Tanium Server. | ||||
| CVE-2026-87033 | 1 Tanium | 1 Comply | 2026-09-10 | 5.4 Medium |
| Tanium addressed an improper access controls vulnerability in Comply. | ||||
| CVE-2026-87035 | 1 Tanium | 1 Comply | 2026-09-10 | 4.3 Medium |
| Tanium addressed an information disclosure vulnerability in Comply. | ||||
| CVE-2026-87034 | 1 Tanium | 1 Comply | 2026-09-10 | 8.3 High |
| Tanium addressed a SQL injection vulnerability in Comply. | ||||
| CVE-2026-87048 | 1 Tanium | 1 Comply | 2026-09-10 | 5.4 Medium |
| Tanium addressed an improper access controls vulnerability in Comply. | ||||
| CVE-2026-87021 | 1 Tanium | 1 Comply | 2026-09-10 | 7.2 High |
| Tanium addressed an unauthorized code execution vulnerability in Comply. | ||||
| CVE-2026-87036 | 1 Tanium | 1 Comply | 2026-09-10 | 8.1 High |
| Tanium addressed an improper access controls vulnerability in Comply. | ||||
| CVE-2026-53956 | 1 Conda | 2 Py-rattler, Rattler | 2026-09-10 | 5.4 Medium |
| Rattler is a library that provides common functionality used within the conda ecosystem. `rattler_cache` prior to version 0.9.0 and `py-rattler` prior to version 0.24.0 were vulnerable to package-cache path traversal when handling package metadata from conda channels. During cache materialization, the `ratter_cache` code used the package record `build` string as part of a cache key that was joined into a filesystem path. A malicious or untrusted channel could publish repodata with path separators or traversal components in that field, causing package contents to be written outside the configured package cache directory. The issue requires use of a malicious or otherwise untrusted conda channel. Curated channels that validate package metadata are not expected to allow malformed build strings of this form. Users should upgrade to `rattler_cache` version 0.9.0 or `py-rattler` version 0.24.0 and avoid untrusted conda channels. | ||||
| CVE-2026-15796 | 2 Builderall, Wordpress | 2 Builder For Wordpress, Wordpress | 2026-09-10 | 6.4 Medium |
| The Builderall for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'bg_video_service_url' Setting in all versions up to, and including, 3.0.2 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. | ||||
| CVE-2026-15823 | 2 Builderall, Wordpress | 2 Builder For Wordpress, Wordpress | 2026-09-10 | 4.3 Medium |
| The Builderall Cheetah For Wp plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the disable() function in versions up to, and including, 3.0.2. The wp_ajax_ba_cheetah_disable AJAX handler is registered without any capability or nonce verification, and the target post_id is sourced directly from user-controlled $_POST['ba_cheetah_data']['post_id']. This makes it possible for authenticated attackers, with Subscriber-level access and above, to disable the page builder layout on arbitrary posts by setting the _ba_cheetah_enabled post meta to false, including on posts owned by other users. | ||||