ChainfroxlorPackagist:froxlor/froxlor
froxlor: incomplete fixes (2026)
3 CVEs over 2 generations, 24 Mar 2026 to 4 Jun 2026.
Family tree
Left to right by publication date.Oldest first. Select a CVE to open it.- CVE-2026-3093224 Mar 2026 First in the chain
- CVE-2026-412344 Jun 2026 incomplete fix for CVE-2026-30932
- CVE-2026-412374 Jun 2026 related to CVE-2026-30932
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-2026-30932 | 24 Mar 2026 | Froxlor is vulnerable to BIND zone file injection via unsanitized DNS record content in DomainZones API · fixed in 2.3.5 | First in chain | 15.4 |
| CVE-2026-41234 | 4 Jun 2026 | Froxlor: BIND Zone File Injection via TXT Record Content | CVE-2026-30932 · incomplete fix · High | 9.2 |
| CVE-2026-41237 | 4 Jun 2026 | Froxlor has an incomplete fix for CVE-2026-30932 | CVE-2026-30932 · related · High | 9.8 |