Unrestricted Upload of File with Dangerous Type in froxlor/froxlor
froxlor · froxlor/froxlor
SummaryAI-written · claude-haiku-5-5AI-written · claude-haiku-5-5Written by a language model from the source data on this page. Not reviewed by a person. Generated 29 Oct 2026.
Froxlor/froxlor, the open-source web hosting control panel, contains an unrestricted file upload flaw (CWE: Unrestricted Upload of File with Dangerous Type) in versions prior to 2.0.14. An attacker who has high-privilege authentication to the application over the network, and no user interaction, can upload files of dangerous types, with high impact to confidentiality, integrity and availability.
Official description · CVE.orgSource dataSource dataCopied from an authoritative feed: NVD, CVE.org, CISA KEV, FIRST EPSS or MITRE CTID mappings, or labelled by the annotators of a published dataset. Copied from CVE.org.
Unrestricted Upload of File with Dangerous Type in GitHub repository froxlor/froxlor prior to 2.0.14.
Priority scorePatchfirst’s 0 to 100 ranking. It adds points for CISA KEV listing, ransomware use, EPSS, threat reports, public exploit code and CVSS. Every CVE page shows the breakdown.Breakdown
26.3 / 100
Exploited
Not confirmed
Reports
0
Tactics
0/15
Exploitation timelineDated milestones for a CVE: when it was disclosed, when exploit code became public, when exploitation was confirmed, and when threat reports named it.
Disclosed on 14 Apr 2023. No public exploit code or confirmed exploitation is recorded.
Patch historyEarlier and later CVEs in the same code, in date order. It shows when a fix was bypassed or incomplete and which version finally fixed it.
7 related vulnerabilities in the same code over 16 months. The latest fix listed for froxlor/froxlor is 2.0.20.
Same bug familyLinked by evidence that a fix failed or the same code was patched again. Oldest first.
CVE-2022-3017Cross-Site Request Forgery (CSRF) in froxlor/froxlor28 Aug 2022
same family
CVE-2022-3721Code Injection in froxlor/froxlor4 Nov 2022
Next fix in the same packageHigh
Why these are linked: 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.
Fixed one release later0.10.38.2 → 0.10.39 (froxlor/froxlor)
Similar weakness in the same product (machine-matched)same product + CWE + description similarity
CVE-2022-3869Code Injection in froxlor/froxlor5 Nov 2022
same family
CVE-2023-0316Path Traversal: '\..\filename' in froxlor/froxlor16 Jan 2023
relatedMedium
Why these are linked: 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.
This CVECVE-2023-2034Unrestricted Upload of File with Dangerous Type in…14 Apr 2023
relatedMedium
Why these are linked: 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.
MITRE ATT&CKA public catalogue of the techniques attackers use, maintained by MITRE. Patchfirst uses it to describe what attackers do with a vulnerability. techniques
No techniques linked
No ATT&CK techniques are linked to this CVE yet. MITRE CTID has not mapped it, and no report passage in the corpus ties it to a technique.
Am I affected? What do I upgrade to?
From GitHub Security Advisories and OSVSourceSource dataCopied from an authoritative feed: NVD, CVE.org, CISA KEV, FIRST EPSS or MITRE CTID mappings, or labelled by the annotators of a published dataset. GitHub Security Advisories and OSV.
1 package in 1 ecosystem. Main package: froxlor/froxlor.