totolink x6000r firmware
ProduktUScpe:2.3:o:totolink:x6000r_firmware:*:*:*:*:*:*:*:*
Ein im Bedrohungsgraphen erfasstes Produkt; die Schwachstellen unten betreffen es bekanntermaßen.
nach Schweregrad
47critical6high1medium0low
aktualisiert 2026-10-28
| ID | Schweregrad CVSS-Basis-Schweregrad und -Wert (0–10). | EPSS FIRST.org-Wahrscheinlichkeit einer Ausnutzung in den nächsten 30 Tagen, mit Perzentil-Rang unter allen CVEs. | ausnutzbar Auf CISAs Liste bekannter ausgenutzter Schwachstellen (KEV) oder ein öffentlicher Exploit liegt vor. | behoben Ob für einen betroffenen Bereich eine behobene Version vorliegt. | veröffentlicht | betroffen |
|---|
| CVE-2024-1781US | critical9.8 | 14.8% (97th) | Exploit | ✗kein Fix | 2024-02-23 | = 9.4.0cu.852_b20230719 |
| CVE-2025-52906US | critical9.8 | 13.5% (96th) | — | ✗kein Fix | 2025-09-24 | ≤ 9.4.0cu.1360_b20241207 |
| CVE-2025-52905US | high7.5 | 8.45% (95th) | — | ✗kein Fix | 2025-09-23 | ≤ 9.4.0cu.1360_b20241207 |
| CVE-2024-7907US | critical9.8 | 6.24% (94th) | — | ✗kein Fix | 2024-08-18 | = 9.4.0cu.852_b20230719 |
| CVE-2025-52053US | — | 4.37% (91st) | — | ✗kein Fix | 2025-09-15 | = 9.4.0cu.1360_b20241207 |
| CVE-2024-2353US | high8.8 | 3.95% (90th) | — | ✗kein Fix | 2024-03-10 | = 9.4.0cu.852_b20230719 |
| CVE-2026-4611US | high8.8 | 3.09% (88th) | — | ✗kein Fix | 2026-03-23 | 2 Versionen |
| CVE-2023-50651US | critical9.8 | 2.80% (86th) | — | ✗kein Fix | 2023-12-30 | = 9.4.0cu.852_b20230719 |
| CVE-2025-52284US | — | 2.25% (83rd) | — | ✗kein Fix | 2025-07-29 | = 9.4.0cu.1360_b20241207 |
| CVE-2023-46424US | critical9.8 | 2.25% (83rd) | — | ✗kein Fix | 2023-10-25 | = 9.4.0cu.652_b20230116 |
| CVE-2023-46423US | critical9.8 | 2.25% (83rd) | — | ✗kein Fix | 2023-10-25 | = 9.4.0cu.652_b20230116 |
| CVE-2023-46422US | critical9.8 | 2.25% (83rd) | — | ✗kein Fix | 2023-10-25 | = 9.4.0cu.652_b20230116 |
| CVE-2023-46421US | critical9.8 | 2.25% (83rd) | — | ✗kein Fix | 2023-10-25 | = 9.4.0cu.652_b20230116 |
| CVE-2023-46420US | critical9.8 | 2.25% (83rd) | — | ✗kein Fix | 2023-10-25 | = 9.4.0cu.652_b20230116 |
| CVE-2023-46419US | critical9.8 | 2.25% (83rd) | — | ✗kein Fix | 2023-10-25 | = 9.4.0cu.652_b20230116 |
| CVE-2023-46418US | critical9.8 | 2.25% (83rd) | — | ✗kein Fix | 2023-10-25 | = 9.4.0cu.652_b20230116 |
| CVE-2023-46417US | critical9.8 | 2.25% (83rd) | — | ✗kein Fix | 2023-10-25 | = 9.4.0cu.652_b20230116 |
| CVE-2023-46416US | critical9.8 | 2.25% (83rd) | — | ✗kein Fix | 2023-10-25 | = 9.4.0cu.652_b20230116 |
| CVE-2023-46415US | critical9.8 | 2.25% (83rd) | — | ✗kein Fix | 2023-10-25 | = 9.4.0cu.652_b20230116 |
| CVE-2023-46414US | critical9.8 | 2.25% (83rd) | — | ✗kein Fix | 2023-10-25 | = 9.4.0cu.652_b20230116 |
| CVE-2025-70328US | high8.8 | 2.04% (81st) | — | ✗kein Fix | 2026-02-23 | = 9.4.0cu.1498_b20250826 |
| CVE-2023-48801US | critical9.8 | 1.69% (77th) | — | ✗kein Fix | 2023-12-01 | = 9.4.0cu.852_b20230719 |
| CVE-2023-48800US | critical9.8 | 1.55% (75th) | — | ✗kein Fix | 2023-12-04 | = 9.4.0cu.852_b20230719 |
| CVE-2023-46413US | critical9.8 | 1.54% (75th) | — | ✗kein Fix | 2023-10-25 | = 9.4.0cu.652_b20230116 |
| CVE-2023-46412US | critical9.8 | 1.54% (75th) | — | ✗kein Fix | 2023-10-25 | = 9.4.0cu.652_b20230116 |
| CVE-2023-46411US | critical9.8 | 1.54% (75th) | — | ✗kein Fix | 2023-10-25 | = 9.4.0cu.652_b20230116 |
| CVE-2023-46410US | critical9.8 | 1.54% (75th) | — | ✗kein Fix | 2023-10-25 | = 9.4.0cu.652_b20230116 |
| CVE-2023-46409US | critical9.8 | 1.54% (75th) | — | ✗kein Fix | 2023-10-25 | = 9.4.0cu.652_b20230116 |
| CVE-2023-46408US | critical9.8 | 1.54% (75th) | — | ✗kein Fix | 2023-10-25 | = 9.4.0cu.652_b20230116 |
| CVE-2023-48812US | critical9.8 | 1.54% (75th) | — | ✗kein Fix | 2023-11-30 | = 9.4.0cu.852_b20230719 |
| CVE-2023-48811US | critical9.8 | 1.54% (75th) | — | ✗kein Fix | 2023-11-30 | = 9.4.0cu.852_b20230719 |
| CVE-2023-48810US | critical9.8 | 1.54% (75th) | — | ✗kein Fix | 2023-11-30 | = 9.4.0cu.852_b20230719 |
| CVE-2023-48808US | critical9.8 | 1.54% (75th) | — | ✗kein Fix | 2023-11-30 | = 9.4.0cu.852_b20230719 |
| CVE-2023-48807US | critical9.8 | 1.54% (75th) | — | ✗kein Fix | 2023-11-30 | = 9.4.0cu.852_b20230719 |
| CVE-2023-48806US | critical9.8 | 1.54% (75th) | — | ✗kein Fix | 2023-11-30 | = 9.4.0cu.852_b20230719 |
| CVE-2023-48805US | critical9.8 | 1.54% (75th) | — | ✗kein Fix | 2023-11-30 | = 9.4.0cu.852_b20230719 |
| CVE-2023-48804US | critical9.8 | 1.54% (75th) | — | ✗kein Fix | 2023-11-30 | = 9.4.0cu.852_b20230719 |
| CVE-2023-48803US | critical9.8 | 1.54% (75th) | — | ✗kein Fix | 2023-11-30 | = 9.4.0cu.852_b20230719 |
| CVE-2023-48802US | critical9.8 | 1.54% (75th) | — | ✗kein Fix | 2023-11-30 | = 9.4.0cu.852_b20230719 |
| CVE-2023-43455US | critical9.8 | 1.52% (74th) | — | ✗kein Fix | 2023-12-01 | 2 Versionen |
| CVE-2023-43454US | critical9.8 | 1.52% (74th) | — | ✗kein Fix | 2023-12-01 | 2 Versionen |
| CVE-2023-43453US | critical9.8 | 1.52% (74th) | — | ✗kein Fix | 2023-12-01 | 2 Versionen |
| CVE-2023-46979US | critical9.8 | 1.52% (74th) | — | ✗kein Fix | 2023-10-31 | = 9.4.0cu.852_b20230719 |
| CVE-2023-48799US | critical9.8 | 1.43% (73rd) | — | ✗kein Fix | 2023-12-04 | = 9.4.0cu.852_b20230719 |
| CVE-2025-11005US | critical9.8 | 1.30% (70th) | — | ✗kein Fix | 2025-09-25 | ≤ 9.4.0cu.1360_b20241207 |
| CVE-2023-46485US | critical9.8 | 1.23% (69th) | — | ✗kein Fix | 2023-10-31 | = 9.4.0cu.852_b20230719 |
| CVE-2023-46484US | critical9.8 | 1.23% (69th) | — | ✗kein Fix | 2023-10-31 | = 9.4.0cu.852_b20230719 |
| CVE-2024-52723US | critical9.8 | 1.02% (63rd) | — | ✗kein Fix | 2024-11-22 | = 9.4.0cu.1041_b20240224 |
| CVE-2023-52042US | critical9.8 | 0.95% (61st) | — | ✗kein Fix | 2024-01-16 | = 9.4.0cu.852_b20230719 |
| CVE-2023-52041US | critical9.8 | 0.86% (58th) | — | ✗kein Fix | 2024-01-16 | = 9.4.0cu.852_b20230719 |
50 von 57 angezeigt