cve.bz

CVE-2023-6069 froxlor froxlor: Link Following

8.8 highExploit referenceEPSS 1.0%Fix available

High (8.8) in froxlor froxlor. EPSS 1.0% estimated probability of exploitation activity in the next 30 days. Fixed in froxlor/froxlor 2.1.0-beta1.

On this page
Improper Link Resolution Before File Access in GitHub repository froxlor/froxlor prior to 2.1.0.

Severity

CVSS 3.1

8.8 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
1.0% (unchanged from 1.0% a week ago; 0.8% 30 days ago) estimated probability of exploitation activity in the next 30 days; 64th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-59 Improper Link Resolution Before File Access (Link Following)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2023-6069 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-6069?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-6069?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2023-6069 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
froxlor/froxlorbefore 2.1.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-4jch-8qq5-hqg6Packagistfroxlor/froxlor<2.1.0-beta12.1.0-beta1

Attack patterns (CAPEC)

  • CAPEC-17 Using Malicious Files Likelihood: High · Severity: Very High
  • CAPEC-35 Leverage Executable Code in Non-Executable Files Likelihood: High · Severity: Very High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-132 Symlink Attack Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON