Export limit exceeded: 372303 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 372303 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 372303 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (372303 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-68500 | 2026-07-31 | 7.5 High | ||
| Sylius Mollie Plugin provides Mollie payment integration for Sylius applications. Prior to 2.2.8, 3.2.4, and 3.3.1, Sylius Mollie Plugin's POST /{_locale}/update-payment payment webhook accepts attacker-controlled id and orderId parameters but does not verify that the Mollie payment belongs to the referenced Sylius order, allowing an unauthenticated attacker with any valid paid Mollie payment ID to mark a victim order as paid without transferring funds for that order. This issue is fixed in 2.2.8, 3.2.4, and 3.3.1. | ||||
| CVE-2026-51304 | 1 Sqlite | 1 Sqlite | 2026-07-31 | 9.8 Critical |
| DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none. | ||||
| CVE-2026-51303 | 1 Sqlite | 1 Sqlite | 2026-07-31 | 9.8 Critical |
| DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none. | ||||
| CVE-2026-51302 | 1 Sqlite | 1 Sqlite | 2026-07-31 | 10.0 Critical |
| DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none. | ||||
| CVE-2026-51300 | 1 Sqlite | 1 Sqlite | 2026-07-31 | 8.1 High |
| DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none. | ||||
| CVE-2026-51298 | 1 Sqlite | 1 Sqlite | 2026-07-31 | 7.5 High |
| DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none. | ||||
| CVE-2026-51297 | 1 Sqlite | 1 Sqlite | 2026-07-31 | 9.8 Critical |
| DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none. | ||||
| CVE-2026-51296 | 1 Sqlite | 1 Sqlite | 2026-07-31 | 8.2 High |
| DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none. | ||||
| CVE-2026-51295 | 1 Sqlite | 1 Sqlite | 2026-07-31 | N/A |
| DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none. | ||||
| CVE-2026-51294 | 1 Sqlite | 1 Sqlite | 2026-07-31 | N/A |
| DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none. | ||||
| CVE-2026-51293 | 1 Sqlite | 1 Sqlite | 2026-07-31 | N/A |
| DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none. | ||||
| CVE-2026-51292 | 1 Sqlite | 1 Sqlite | 2026-07-31 | N/A |
| DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none. | ||||
| CVE-2026-51291 | 1 Sqlite | 1 Sqlite | 2026-07-31 | N/A |
| DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none. | ||||
| CVE-2026-51290 | 1 Sqlite | 1 Sqlite | 2026-07-31 | N/A |
| DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none. | ||||
| CVE-2026-51275 | 1 Schreibfaul1 | 1 Esp32-audioi2s | 2026-07-31 | N/A |
| DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none. | ||||
| CVE-2026-51274 | 1 Schreibfaul1 | 1 Esp32-audioi2s | 2026-07-31 | N/A |
| DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none. | ||||
| CVE-2026-51273 | 1 Schreibfaul1 | 1 Esp32-audioi2s | 2026-07-31 | N/A |
| DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none. | ||||
| CVE-2026-51272 | 1 Schreibfaul1 | 1 Esp32-audioi2s | 2026-07-31 | N/A |
| DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none. | ||||
| CVE-2026-51271 | 1 Schreibfaul1 | 1 Esp32-audioi2s | 2026-07-31 | N/A |
| DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none. | ||||
| CVE-2026-51270 | 1 Schreibfaul1 | 1 Esp32-audioi2s | 2026-07-31 | N/A |
| DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none. | ||||