Overview 7 matches · 0 in Waratek scope · 0 protected · 0 CISA KEV · 3 public PoC · 0 EPSS ≥ 0.5
Protected by Waratek
0
0.0%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
0
0.0%
Outside Waratek scope
0
0.0%
Not applicable
1
14.3%
Withdrawn CVE
6
85.7%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
7
100.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
7
100.0%
Working exploit published
0
0.0%
Proof of concept only
0
0.0%
Forecast only
0
0.0%
No public exploit
0
0.0%
split by
peak 2 / year
20171
Withdrawn CVE1
Unknown1
not blocked1
Exploited1
20180
20191
Withdrawn CVE1
Unknown1
not blocked1
Exploited1
20200
20210
20220
20231
Withdrawn CVE1
Unknown1
not blocked1
Exploited1
20241
Not applicable1
Unknown1
not blocked1
Exploited1
20252
Withdrawn CVE2
Unknown2
not blocked2
Exploited2
20261
Withdrawn CVE1
Unknown1
not blocked1
Exploited1
2017201820192020202120222023202420252026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2024-58388 | Unknown | 2026-10-01 | Withdrawn CVE | Exploited | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. CVE-2024-33605's description was updated to include the impacted endpoint as singular patch addressed both. |
| CVE-2025-2825 | Unknown | 2025-03-26 | Withdrawn CVE | Exploited | Rejected reason: DO NOT USE THIS CVE RECORD. ConsultIDs: CVE-2025-31161. Reason: This Record is a reservation duplicate of CVE-2025-31161. Notes: All CVE users should reference CVE-2025-31161 instead of this Record. All references and descriptions in this Record have been removed to prevent accidental usage. |
| CVE-2024-57049 | Unknown | 2025-02-18 | Withdrawn CVE | Exploited | Rejected reason: 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-2024-29291 | Unknown | 2024-04-16 | Not applicable | Exploited | An issue in Laravel Framework 8 through 11 might allow a remote attacker to discover database credentials in storage/logs/laravel.log. NOTE: this is disputed by multiple third parties because the owner of a Laravel Framework installation can choose to have debugging logs, but needs to set the access control appropriately for the type of data that may be logged. |
| CVE-2021-0027 | Unknown | 2023-05-16 | Withdrawn CVE | Exploited | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was in a CNA pool that was not assigned to any issues during 2021. Notes: none. |
| CVE-2019-9081 | Unknown | 2019-02-24 | Withdrawn CVE | Exploited | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none |
| CVE-2015-2551 | Unknown | 2017-05-11 | Withdrawn CVE | Exploited | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability during 2015. Notes: none |