CVE-2023-0315

HIGHNVD 8.89.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because EPSS predicts 98% probability of exploitation within the next 30 days (top 0.1% of all CVEs). NVD baseline CVSS 8.8 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, nvd
Weaponized
8.8
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 98%
CISA-KEV: Not listedEPSS: 98%CVSS: 8.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Command Injection in GitHub repository froxlor/froxlor prior to 2.0.8.

CVSS v3
8.8
EG Score
9.0(high)
EG Risk
80(Track*)
EG Risk 80/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity90% × 45%
Exploitation98% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS
99.9%
KEV
Not listed

Published

January 16, 2023

Last Modified

November 21, 2024

References (8)

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFixed inDependents
froxlor/froxlor0.10.0 ... 2.0.7 (56 versions)2.0.8—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 5× in last 7d / 14× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-24 14:15 UTCEPSS rescore
  2. 2026-07-23 02:17 UTCEG score recompute
  3. 2026-07-22 23:04 UTCEG score recompute
  4. 2026-07-22 14:06 UTCEPSS rescore
  5. 2026-07-22 14:06 UTCEPSS rescore
  6. 2026-07-16 08:49 UTCOSV refresh
  7. 2026-07-09 19:08 UTCEPSS rescore
  8. 2026-07-05 02:28 UTCEPSS rescore
  9. 2026-07-01 15:04 UTCEPSS rescore
  10. 2026-06-30 23:21 UTCEPSS rescore
  11. 2026-06-30 23:20 UTCEPSS rescore
  12. 2026-06-28 08:21 UTCOSV refresh
  13. 2026-06-27 03:07 UTCEPSS rescore
  14. 2026-06-27 03:07 UTCEPSS rescore
  15. 2026-06-23 21:31 UTCEPSS rescore
  16. 2026-06-23 21:31 UTCEPSS rescore
  17. 2026-06-15 17:47 UTCEPSS rescore
  18. 2026-06-14 23:16 UTCEPSS rescore
  19. 2026-06-13 22:59 UTCEPSS rescore
  20. 2026-06-10 18:47 UTCOSV refresh
  21. 2026-06-10 13:21 UTCEPSS rescore
  22. 2026-06-10 13:21 UTCEPSS rescore
  23. 2026-06-05 22:46 UTCEPSS rescore
  24. 2026-06-05 22:46 UTCEPSS rescore
  25. 2026-06-05 06:09 UTCEPSS rescore
Show 19 more
  1. 2026-06-05 06:09 UTCEPSS rescore
  2. 2026-06-04 13:11 UTCEPSS rescore
  3. 2026-06-01 13:50 UTCEPSS rescore
  4. 2026-06-01 13:50 UTCEPSS rescore
  5. 2026-05-31 22:29 UTCEPSS rescore
  6. 2026-05-31 22:29 UTCEPSS rescore
  7. 2026-05-29 13:43 UTCEPSS rescore
  8. 2026-05-28 13:43 UTCEPSS rescore
  9. 2026-05-28 13:43 UTCEPSS rescore
  10. 2026-05-27 13:39 UTCEPSS rescore
  11. 2026-05-27 13:39 UTCEPSS rescore
  12. 2026-05-26 13:43 UTCEPSS rescore
  13. 2026-05-26 13:43 UTCEPSS rescore
  14. 2026-05-26 13:43 UTCEPSS rescore
  15. 2026-05-26 07:17 UTCEPSS rescore
  16. 2026-05-26 07:17 UTCEPSS rescore
  17. 2026-05-26 07:17 UTCEPSS rescore
  18. 2026-05-25 08:35 UTCEG score recompute
  19. 2026-05-24 17:12 UTCOSV refresh

Publicly available exploits

(3 references)

Working exploit code is in the public domain (1 Metasploit module) (1 GitHub PoC) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-51263
    First seen Apr 5, 2023

    Froxlor 2.0.3 Stable - Remote Code Execution (RCE)

    Open source ↗
  • GitHub PoCmhaskar/CVE-2023-0315
    First seen Jan 29, 2023

    The official exploit for Froxlor Remote Code Execution CVE-2023-0315

    Open source ↗
  • Metasploitexploit/linux/http/froxlor_log_path_rce✓ verified
    First seen Jan 29, 2023

    Froxlor Log Path RCE

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2023-0315?
CVE-2023-0315 is a high vulnerability published on January 16, 2023. Command Injection in GitHub repository froxlor/froxlor prior to 2.0.8.
When was CVE-2023-0315 disclosed?
CVE-2023-0315 was first published in the National Vulnerability Database on January 16, 2023, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-0315 actively exploited?
CVE-2023-0315 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2023-0315?
CVE-2023-0315 has a CVSS v3 base score of 8.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
How do I remediate CVE-2023-0315?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-0315, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-0315

Explore →

Is Your Infrastructure Affected by CVE-2023-0315?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs