Chainfroxlor/froxlorPackagist:froxlor/froxlor
froxlor/froxlor: successive fixes (2023–2024)
4 CVEs over 3 generations, 16 Jan 2023 to 10 May 2024.
Family tree
Left to right by publication date.Oldest first. Select a CVE to open it.- CVE-2023-031516 Jan 2023 First in the chain
- CVE-2023-266612 May 2023 related to CVE-2023-0315
- CVE-2023-31739 Jun 2023 related to CVE-2023-2666related to CVE-2023-0315
- CVE-2024-3407010 May 2024 related to CVE-2023-0315
Exploited in the wild (CISA KEV) Not in KEV Priority score (0 to 100) High confidence Medium Low Link confidenceHow strong the evidence is that two CVEs are related. High: stated in the CVE text or linked in an advisory, or the same code was patched one release apart. Medium: the same code, or a version step plus a similar description. Low: similar description only.
CVEs in this family
Table view of the tree| CVE | Published | Title | Linked from | Priority |
|---|---|---|---|---|
| CVE-2023-0315 | 16 Jan 2023 | Command Injection in froxlor/froxlor · fixed in 2.0.8 | First in chain | 30.0 |
| CVE-2023-2666 | 12 May 2023 | Allocation of Resources Without Limits or Throttling in froxlor/froxlor · fixed in 2.0.16 | CVE-2023-0315 · related · Medium | 15.2 |
| CVE-2023-3173 | 9 Jun 2023 | Improper Restriction of Excessive Authentication Attempts in froxlor/froxlor · fixed in 2.0.20 | CVE-2023-2666 · related · High | 20.1 |
| CVE-2024-34070 | 10 May 2024 | Froxlor Vulnerable to Blind XSS Leading to Froxlor Application Compromise · fixed in 2.1.9 | CVE-2023-0315 · related · Medium | 24.2 |