Export limit exceeded: 382100 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (382100 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-78306 | 2026-08-24 | N/A | ||
| DJI drones expose an unauthenticated DUML command interface over Bluetooth that allows an attacker within Bluetooth range to modify Wi-Fi configuration parameters, including the SSID, PSK, MAC address, regulatory country code, and wireless channel. An attacker can overwrite the Wi-Fi PSK with a known value and connect to the drone's internal Wi-Fi network, potentially gaining access to the flight control interface and issuing flight commands. Crafted DUML commands can also disable or restart the Wi-Fi and Bluetooth interfaces, disconnect Wi-Fi clients, or reset wireless configuration, resulting in a denial-of-service condition that can disrupt the operator's wireless control, video, and telemetry connections during flight. Affected models are DJI Neo until 01.00.0400, DJI Neo 2 until 01.00.0500, DJI Flip until 01.00.1200, DJI Air 3 until 01.00.1600, DJI Air 3S until 01.00.1400, DJI Avata 2 until 01.00.0400, DJI Avata 360 until 01.00.0300, DJI Mavic 3 until 01.00.1400, DJI Mavic 3 Classic until 01.00.0800, DJI Mavic 3 Pro until 01.01.0700, DJI Mavic 4 Pro until 01.00.0500, DJI Mini 2 until 01.07.0200, DJI Mini 3 until 01.00.0500, DJI Mini 3 Pro until 01.00.0900, DJI Mini 4 Pro until 01.00.1100, and DJI Mini 5 Pro until 01.00.0600. Remediation requires a firmware update from the vendor. | ||||
| CVE-2026-78291 | 2 Webful Creations, Wordpress | 2 Repairbuddy, Wordpress | 2026-08-24 | 5.3 Medium |
| Unauthenticated Broken Access Control in RepairBuddy <= 4.1223 versions. | ||||
| CVE-2026-78290 | 2 Themegrill, Wordpress | 2 Magazine Blocks, Wordpress | 2026-08-24 | 6.5 Medium |
| Contributor Cross Site Scripting (XSS) in Magazine Blocks <= 1.8.6 versions. | ||||
| CVE-2026-78280 | 2 Hashthemes, Wordpress | 2 Hash Form, Wordpress | 2026-08-24 | 4.3 Medium |
| Unauthenticated Cross Site Request Forgery (CSRF) in Hash Form <= 1.4.0 versions. | ||||
| CVE-2026-78279 | 2026-08-24 | 5.4 Medium | ||
| Unauthenticated Cross Site Request Forgery (CSRF) in Fluent Support Pro <= 2.3.1 versions. | ||||
| CVE-2026-78278 | 2026-08-24 | 5.3 Medium | ||
| Subscriber Insecure Direct Object References (IDOR) in Fluent Boards Pro <= 2.0.11 versions. | ||||
| CVE-2026-78277 | 2026-08-24 | 4.9 Medium | ||
| Subscriber Server Side Request Forgery (SSRF) in FluentCRM Pro <= 3.1.12 versions. | ||||
| CVE-2026-78272 | 2026-08-24 | 5.4 Medium | ||
| Subscriber Broken Access Control in Fluent Support Pro <= 2.3.1 versions. | ||||
| CVE-2026-78270 | 2026-08-24 | 7.6 High | ||
| Author SQL Injection in FluentCRM Pro <= 3.1.12 versions. | ||||
| CVE-2026-78211 | 2026-08-24 | 9.8 Critical | ||
| 4MOSAn GCB Doctor developed by 4MOSAn Security Technology has a OS Command Injection vulnerability. Unauthenticated remote attackers can inject malicious commands through an unremoved ADOdb test page parameter, thereby executing arbitrary system commands on the server. | ||||
| CVE-2026-69555 | 1 Microsoft | 1 Azure Arc | 2026-08-24 | 10 Critical |
| Incorrect authorization in Azure Arc allows an unauthorized attacker to elevate privileges over a network. | ||||
| CVE-2026-66671 | 2026-08-24 | 8.1 High | ||
| Unauthenticated Local File Inclusion in Verdure Core <= 1.2 versions. | ||||
| CVE-2026-66670 | 2026-08-24 | 8.1 High | ||
| Unauthenticated Local File Inclusion in Måne <= 1.7 versions. | ||||
| CVE-2026-66650 | 2026-08-24 | 9.8 Critical | ||
| Unauthenticated PHP Object Injection in FreightCo <= 1.1.15 versions. | ||||
| CVE-2026-66648 | 2026-08-24 | 9.8 Critical | ||
| Unauthenticated Privilege Escalation in Jawn <= 1.4.2 versions. | ||||
| CVE-2026-66587 | 2026-08-24 | 9.8 Critical | ||
| Unauthenticated Local File Inclusion in WP Cafe Pro < 3.0.15 versions. | ||||
| CVE-2026-66585 | 2026-08-24 | 7.5 High | ||
| Unauthenticated Sensitive Data Exposure in WP Cafe Pro < 3.0.15 versions. | ||||
| CVE-2026-66584 | 2026-08-24 | 7.1 High | ||
| Unauthenticated Cross Site Scripting (XSS) in 12 Step Meeting List <= 3.19.16 versions. | ||||
| CVE-2026-78378 | 2026-08-24 | N/A | ||
| Ransomlook contains a Redis glob pattern injection vulnerability caused by insufficient neutralization of user-controlled input before it is incorporated into Redis SCAN MATCH patterns. The /api/health/<name> endpoint attempted to resolve the supplied name to a known group or market, but when resolution failed it fell back to using the attacker-controlled value directly in a Redis key pattern. An unauthenticated attacker could therefore supply Redis glob metacharacters such as *, ?, [ or ] to broaden the SCAN operation beyond the intended group. For example, requesting /api/health/* could enumerate health information, mirror slugs, and uptime series belonging to all groups and markets, including entities marked as private. Similar unsafe interpolation was present in /api/crypto/chain/<chain> and in the delete_manual_torrent() function. The latter represents a potentially destructive sink because a crafted infohash containing glob metacharacters could cause the scan to match torrent-health keys belonging to other torrents if attacker-controlled input can reach that function. The patch removes the unsafe fallback from the health endpoint and introduces glob escaping for user-controlled values before they are incorporated into Redis SCAN MATCH expressions. | ||||
| CVE-2026-45447 | 1 Openssl | 1 Openssl | 2026-08-24 | 8.8 High |
| Issue summary: A specially crafted PKCS#7 or S/MIME signed message could trigger a use-after-free during PKCS#7 signature verification. Impact summary: A use-after-free may result in process crashes, heap corruption, or potentially remote code execution. When processing a PKCS#7 or S/MIME signed message, if the SignedData digestAlgorithms field is present as an empty ASN.1 SET, OpenSSL may incorrectly free a caller-owned BIO during PKCS7_verify(). A subsequent use of the BIO by the calling application results in a use-after-free condition. In the common case this occurs when the application later calls BIO_free() on the BIO originally passed to PKCS7_verify(). Depending on allocator behavior and application-specific BIO usage patterns, this may result in a crash or other memory corruption. In some application contexts this may potentially be exploitable for remote code execution. Applications that process PKCS#7 or S/MIME signed messages using OpenSSL PKCS#7 APIs may be affected. Applications using the CMS APIs for this processing are not affected. The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary. | ||||