CVE-2023-0315

CRITICALNVD 8.89.0
EchelonGraph scoreHIGH confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score elevated to 9.0 because EPSS predicted 98% probability of exploitation within the next 30 days (99th percentile of EPSS-scored CVEs) when EchelonGraph scored this CVE. NVD baseline CVSS 8.8 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction (continuous uplift above 30%)
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Weaponized

Also known asEUVD-2023-0448 (ENISA EUVD) · GHSA-cp68-42pf-6627 (GitHub Security Advisories)Source: ENISA EUVD

9.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High exploitation likelihood — EPSS 98%
  • Public exploit code is available (Metasploit, other public proof-of-concept code)
CISA-KEV: Not listedEPSS PROB: 98%CVSS: 8.8Exploit: Metasploit · other public PoCExposed services: Not assessed

A fix is available — apply it.

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

CVSS v3
8.8
EG Score
9.0CRITICALhigh confidence
EG Risk
79
EG Risk 79/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation98% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
98%
EPSS %ILE
99th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is EPSS's lift toward 9.0 from its impact severity (EG Severity, CVSS 8.8 HIGH): a likelihood of exploitation, not impact.

EG Severity
8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
98% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

January 16, 2023

Last Modified

November 21, 2024

Advisory Details (2)

Auto-updated Aug 24, 2026
Patch available. Sources: github_commit.
Web page

huntr - The world's first bug bounty platform for AI/ML

https://huntr.dev/bounties/ff4e177b-ba48-4913-bbfa-ab8ce0db5943
GitHub commit Patch Available

commit 090cfc26f272 (froxlor/froxlor)

Patch available: froxlor/froxlor 2.1.3 (contains commit 090cfc26f272)

https://github.com/froxlor/froxlor/commit/090cfc26f2722ac3036cc7fd1861955bc36f065a

Vendor Advisories for CVE-2023-0315(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
composerfroxlor/froxlor @ 2.0.8 (fixes < 2.0.8)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFix by version rangeDependents
froxlor/froxlor0.10.0 ... 2.0.7 (56 versions)
  • every version up to 2.0.8: fixed in 2.0.8
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 18× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 111 rows on record for this CVE, as 91 entries (9 repeats merged).

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 9 repeat rows among the latest 100 are merged into the row they repeat. The 11 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-12 18:24 UTCEchelonGraph re-scored
  2. 2026-11-12 18:24 UTCGHSA enrichmentGHSA-cp68-42pf-6627 · GitHub severity HIGH · GitHub CVSS 8.8
  3. 2026-11-11 17:54 UTCEchelonGraph re-scored
  4. 2026-11-11 17:54 UTCGHSA enrichmentGHSA-cp68-42pf-6627 · GitHub severity HIGH · GitHub CVSS 8.8
  5. 2026-11-11 16:33 UTCEPSS rescoreEPSS 98% · 99th percentile
  6. 2026-11-10 17:24 UTCEchelonGraph re-scored
  7. 2026-11-10 17:24 UTCGHSA enrichmentGHSA-cp68-42pf-6627 · GitHub severity HIGH · GitHub CVSS 8.8
  8. 2026-11-09 16:54 UTCEchelonGraph re-scored
  9. 2026-11-09 16:54 UTCGHSA enrichmentGHSA-cp68-42pf-6627 · GitHub severity HIGH · GitHub CVSS 8.8
  10. 2026-11-08 16:25 UTCEchelonGraph re-scored
  11. 2026-11-08 16:25 UTCGHSA enrichmentGHSA-cp68-42pf-6627 · GitHub severity HIGH · GitHub CVSS 8.8
  12. 2026-11-07 15:51 UTCEchelonGraph re-scored
  13. 2026-11-07 15:51 UTCGHSA enrichmentGHSA-cp68-42pf-6627 · GitHub severity HIGH · GitHub CVSS 8.8
  14. 2026-11-06 15:22 UTCEchelonGraph re-scored
  15. 2026-11-06 15:22 UTCGHSA enrichmentGHSA-cp68-42pf-6627 · GitHub severity HIGH · GitHub CVSS 8.8
  16. 2026-11-05 14:53 UTCEchelonGraph re-scored
  17. 2026-11-05 14:53 UTCGHSA enrichmentGHSA-cp68-42pf-6627 · GitHub severity HIGH · GitHub CVSS 8.8
  18. 2026-11-04 14:23 UTCEchelonGraph re-scored
  19. 2026-11-04 14:23 UTCGHSA enrichmentGHSA-cp68-42pf-6627 · GitHub severity HIGH · GitHub CVSS 8.8
  20. 2026-11-04 09:25 UTCOSV refresh
  21. 2026-11-03 13:53 UTCEchelonGraph re-scored
  22. 2026-11-03 13:53 UTCGHSA enrichmentGHSA-cp68-42pf-6627 · GitHub severity HIGH · GitHub CVSS 8.8
  23. 2026-11-02 13:09 UTCEchelonGraph re-scored
  24. 2026-11-02 13:09 UTCGHSA enrichmentGHSA-cp68-42pf-6627 · GitHub severity HIGH · GitHub CVSS 8.8
  25. 2026-11-01 12:36 UTCGHSA enrichmentGHSA-cp68-42pf-6627 · GitHub severity HIGH · GitHub CVSS 8.8
Show 66 more
  1. 2026-11-01 08:23 UTCGHSA enrichmentGHSA-cp68-42pf-6627 · GitHub severity HIGH · GitHub CVSS 8.8
  2. 2026-11-01 08:23 UTCEchelonGraph re-scored
  3. 2026-10-31 12:07 UTCEchelonGraph re-scored
  4. 2026-10-30 16:31 UTCEPSS rescoreEPSS 98% · 99th percentile
  5. 2026-10-30 11:37 UTCEchelonGraph re-scored
  6. 2026-10-29 11:06 UTCEchelonGraph re-scored
  7. 2026-10-28 10:29 UTCEchelonGraph re-scored
  8. 2026-10-27 09:09 UTCEchelonGraph re-scored
  9. 2026-10-25 17:53 UTCEchelonGraph re-scored
  10. 2026-10-25 16:29 UTCEPSS rescoreEPSS 98% · 99th percentile
  11. 2026-10-25 07:19 UTCEchelonGraph re-scored
  12. 2026-10-24 06:49 UTCEchelonGraph re-scored
  13. 2026-10-23 06:20 UTCEchelonGraph re-scored
  14. 2026-10-22 05:50 UTCEchelonGraph re-scored
  15. 2026-10-21 16:29 UTCEPSS rescoreEPSS 98% · 99th percentile
  16. 2026-10-21 05:18 UTCEchelonGraph re-scored
  17. 2026-10-20 04:47 UTCEchelonGraph re-scored
  18. 2026-10-19 04:16 UTCEchelonGraph re-scored
  19. 2026-10-18 03:44 UTCEchelonGraph re-scored
  20. 2026-10-17 03:13 UTCEchelonGraph re-scored
  21. 2026-10-16 02:43 UTCEchelonGraph re-scored
  22. 2026-10-14 22:43 UTCEchelonGraph re-scored
  23. 2026-10-14 16:29 UTCEPSS rescoreEPSS 98% · 99th percentile
  24. 2026-10-13 18:19 UTCEchelonGraph re-scored
  25. 2026-10-12 17:46 UTCEchelonGraph re-scored
  26. 2026-10-11 22:03 UTCEchelonGraph re-scored
  27. 2026-09-30 16:13 UTCEchelonGraph re-scored
  28. 2026-09-24 14:00 UTCEPSS rescoreEPSS 98% · 99th percentile
  29. 2026-09-23 23:11 UTCOSV refresh
  30. 2026-09-20 20:13 UTCEPSS rescoreEPSS 98% · 99th percentile
  31. 2026-09-06 13:45 UTCEPSS rescoreEPSS 98% · 99th percentile
  32. 2026-09-05 15:25 UTCEPSS rescoreEPSS 98% · 99th percentile
  33. 2026-09-04 17:54 UTCOSV refresh
  34. 2026-08-30 19:15 UTCEPSS rescoreEPSS 98% · 99th percentile
  35. 2026-08-28 21:38 UTCEPSS rescoreEPSS 98% · 99th percentile
  36. 2026-08-25 13:46 UTCEPSS rescoreEPSS 98% · 99th percentile
  37. 2026-08-20 22:53 UTCEPSS rescoreEPSS 98% · 99th percentile
  38. 2026-08-18 05:04 UTCOSV refresh
  39. 2026-08-15 01:27 UTCEPSS rescoreEPSS 98% · 99th percentile
  40. 2026-08-05 19:15 UTCEPSS rescoreEPSS 98% · 99th percentile
  41. 2026-08-02 23:57 UTCOSV refresh
  42. 2026-07-25 14:16 UTCEPSS rescoreEPSS 98% · 99th percentile
  43. 2026-07-24 14:15 UTCEPSS rescoreEPSS 98% · 99th percentile
  44. 2026-07-23 02:17 UTCEchelonGraph re-scored
  45. 2026-07-22 23:04 UTCEchelonGraph re-scored
  46. 2026-07-22 14:06 UTCEPSS rescoreEPSS 98% · 99th percentile
  47. 2026-07-16 08:49 UTCOSV refresh
  48. 2026-07-09 19:08 UTCEPSS rescoreEPSS 98% · 99th percentile
  49. 2026-07-05 02:28 UTCEPSS rescoreEPSS 98% · 99th percentile
  50. 2026-07-01 15:04 UTCEPSS rescoreEPSS 98% · 99th percentile
  51. 2026-06-30 23:20 UTCEPSS rescoreEPSS 98% · 99th percentile
  52. 2026-06-28 08:21 UTCOSV refresh
  53. 2026-06-27 03:07 UTCEPSS rescoreEPSS 98% · 99th percentile
  54. 2026-06-23 21:31 UTCEPSS rescoreEPSS 98% · 99th percentile
  55. 2026-06-15 17:47 UTCEPSS rescoreEPSS 98% · 99th percentile
  56. 2026-06-14 23:16 UTCEPSS rescoreEPSS 89% · 99th percentile
  57. 2026-06-13 22:59 UTCEPSS rescoreEPSS 89% · 99th percentile
  58. 2026-06-10 18:47 UTCOSV refresh
  59. 2026-06-10 13:21 UTCEPSS rescoreEPSS 89% · 99th percentile
  60. 2026-06-05 22:46 UTCEPSS rescoreEPSS 89% · 99th percentile
  61. 2026-06-05 06:09 UTCEPSS rescoreEPSS 89% · 99th percentile
  62. 2026-06-04 13:11 UTCEPSS rescoreEPSS 89% · 99th percentile
  63. 2026-06-01 13:50 UTCEPSS rescoreEPSS 89% · 99th percentile
  64. 2026-05-31 22:29 UTCEPSS rescoreEPSS 89% · 99th percentile
  65. 2026-05-29 13:43 UTCEPSS rescoreEPSS 89% · 99th percentile
  66. 2026-05-28 13:43 UTCEPSS rescoreEPSS 89% · 99th percentile

Publicly available exploits

(3 references)

Public exploit code is referenced for this CVE (1 Metasploit module, 1 Exploit-DB entry, 1 GitHub PoC). Defenders should treat patch urgency accordingly.

  • Metasploitexploit/linux/http/froxlor_log_path_rce✓ verified
    Published Feb 22, 2023

    Froxlor Log Path RCE

    Open source ↗
  • Exploit-DBEDB-51263
    Published Apr 5, 2023

    Froxlor 2.0.3 Stable - Remote Code Execution (RCE)

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

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

    Open source ↗

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2023-0315?
CVE-2023-0315 is a critical-severity vulnerability; its CVE record was published on January 16, 2023. Command Injection in GitHub repository froxlor/froxlor prior to 2.0.8.
When was the CVE record for CVE-2023-0315 published?
The CVE record for CVE-2023-0315 was published on January 16, 2023. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 21, 2024; the record at its source may have been updated since.
Is CVE-2023-0315 actively exploited?
CVE-2023-0315 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model places it in Tier 2 (Weaponized), which is not evidence of exploitation: a Metasploit module exists for it, and CISA's SSVC data says a public PoC exists and its EPSS is 50% or more. EchelonGraph does not test whether exploit code works. FIRST EPSS estimates a 98% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
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 + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
How do I remediate CVE-2023-0315?
A fix for CVE-2023-0315 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-0315 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs