CVE-2023-6069 json
Improper Link Resolution Before File Access in froxlor/froxlor
published 3y ago modified 4mo ago also GHSA-4jch-8qq5-hqg6 , EUVD-2023-2879
- cvss
- 9.9
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 63%
- public exploits
- 0
- none known
Summary
Improper Link Resolution Before File Access in GitHub repository froxlor/froxlor prior to 2.1.0.
Patch / fix
- packagist froxlor/froxlor 2.1.0-beta1
- froxlor froxlor/froxlor 2.1.0
Is CVE-2023-6069 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.01% chance of exploitation in the next 30 days, higher than 63% of all scored CVEs (FIRST EPSS, 2026-11-15).
Exploits and checks
- huntr.com https://huntr.com/bounties/aac0627e-e59d-476e-9385-edb7ff53758c referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.9 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H |
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| GitHub | 3.0 | 9.9 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | froxlor/froxlor | <2.1.0-beta1 |
2.1.0-beta1 |
Affected products
- froxlor froxlor/froxlor
Classification
- Weakness
-
- CWE-59 Improper Link Resolution Before File Access
References
-
github.com
/froxlor/froxlor/commit/9e8f32f1e86016733b603b50c31b97f472e8dabc
web, patch
-
huntr.com
/bounties/aac0627e-e59d-476e-9385-edb7ff53758c
web, exploit, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2023-6069
advisory
-
github.com
/froxlor/froxlor
package
Sources
- CVE List CVE-2023-6069
- GitHub Advisory GHSA-4jch-8qq5-hqg6
- NVD CVE-2023-6069
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.