CVE-2024-58383

HIGHPre-NVD 7.37.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.3 from GitHub Security Advisory (severity: HIGH) published 2026-09-14. A secondary CVSS source baseline 7.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated

Also known asEUVD-2024-55764 (ENISA EUVD) · GHSA-x2wh-r8m8-h3h3 (GitHub Security Advisories)Source: ENISA EUVD

7.3EG
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).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.3Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Froxlor before 2.2.0 (affected up to and including 2.2.0-rc3) generates /etc/pure-ftpd/db/mysql.conf with mode 0644 via the XML configuration templates in lib/configfiles/, even though the file contains the Froxlor SQL user's password. On systems where the parent directories are world readable (the default on Debian 12), any unprivileged local user able to execute commands or code on the host — including virtual users without SSH access who can upload PHP/CGI scripts — can read the file and obtain the Froxlor database credentials. Database access can then be leveraged to alter an administrator's password hash and TOTP seed, log in as a Froxlor administrator, and ultimately gain root privileges. Only instances configured to use pure-ftpd are affected.

CVSS v3
7.3
EG Score
7.3HIGHmedium confidence
EG Risk
49
EG Risk 49/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)
Severity73% × 45%
Impact severity (EG Severity): CVSS 7.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
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
0.2%
EPSS %ILE
4th
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 (7.3): severity, escalated by confirmed exploitation. This CVE's 7.3 is its impact severity (EG Severity), not escalated.

EG Severity
7.3 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-10). 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

September 14, 2026

Last Modified

October 27, 2026

Advisory Details (2)

Auto-updated Sep 14, 2026
Patch available. Sources: github.
Web page

Froxlor before 2.2.0 Insecure File Permissions mysql.conf | Advisories | VulnCheck

https://www.vulncheck.com/advisories/froxlor-before-2.2.0-insecure-file-permissions-mysql-conf
GitHub advisoryMentions a patch (unverified)

/etc/pure-ftpd/db/mysql.conf is chmod 644 but contains <SQL_UNPRIVILEGED_PASSWORD> · Advisory · froxlor/froxlor · GitHub

https://github.com/froxlor/froxlor/security/advisories/GHSA-34qg-65m4-f23m

Vendor Advisories for CVE-2024-58383(1)

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

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFix by version rangeDependents
froxlor/froxlor0.10.0 ... 2.2.0-rc3 (91 versions)
  • every version up to 2.2.0: fixed in 2.2.0
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 30× 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 150 rows on record for this CVE, as 98 entries (2 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. 2 repeat rows among the latest 100 are merged into the row they repeat. The 50 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 16:48 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  2. 2026-11-12 16:31 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  3. 2026-11-11 16:35 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  4. 2026-11-11 05:07 UTCEchelonGraph re-scored
  5. 2026-11-11 05:07 UTCGHSA enrichmentGHSA-x2wh-r8m8-h3h3 · GitHub severity HIGH · GitHub CVSS 7.3
  6. 2026-11-10 16:39 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  7. 2026-11-09 16:32 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  8. 2026-11-07 16:36 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  9. 2026-11-06 16:32 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  10. 2026-11-05 16:34 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  11. 2026-11-04 16:32 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  12. 2026-11-03 19:41 UTCEchelonGraph re-scored
  13. 2026-11-03 19:41 UTCGHSA enrichmentGHSA-x2wh-r8m8-h3h3 · GitHub severity HIGH · GitHub CVSS 7.3
  14. 2026-11-03 16:43 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  15. 2026-11-02 16:41 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  16. 2026-11-01 16:32 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  17. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  18. 2026-10-30 16:32 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  19. 2026-10-29 16:31 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  20. 2026-10-28 16:30 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  21. 2026-10-27 23:27 UTCEchelonGraph re-scored
  22. 2026-10-27 23:27 UTCGHSA enrichmentGHSA-x2wh-r8m8-h3h3 · GitHub severity HIGH · GitHub CVSS 7.3
  23. 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  24. 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  25. 2026-10-25 16:53 UTCEchelonGraph re-scored
Show 73 more
  1. 2026-10-25 16:30 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  2. 2026-10-24 16:30 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  3. 2026-10-22 00:53 UTCEchelonGraph re-scored
  4. 2026-10-22 00:53 UTCGHSA enrichmentGHSA-x2wh-r8m8-h3h3 · GitHub severity HIGH · GitHub CVSS 7.3
  5. 2026-10-21 16:30 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  6. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  7. 2026-10-19 16:30 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  8. 2026-10-18 16:30 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  9. 2026-10-18 05:57 UTCEchelonGraph re-scored
  10. 2026-10-16 16:37 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  11. 2026-10-15 16:30 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  12. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  13. 2026-10-14 15:37 UTCEchelonGraph re-scored
  14. 2026-10-14 15:36 UTCGHSA enrichmentGHSA-x2wh-r8m8-h3h3 · GitHub severity HIGH · GitHub CVSS 7.3
  15. 2026-10-13 16:31 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  16. 2026-10-12 17:36 UTCEchelonGraph re-scored
  17. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  18. 2026-10-11 21:02 UTCEchelonGraph re-scored
  19. 2026-10-11 15:53 UTCEchelonGraph re-scored
  20. 2026-10-11 13:46 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  21. 2026-10-11 12:17 UTCEchelonGraph re-scored
  22. 2026-10-11 12:17 UTCGHSA enrichmentGHSA-x2wh-r8m8-h3h3 · GitHub severity HIGH · GitHub CVSS 7.3
  23. 2026-10-10 22:59 UTCEchelonGraph re-scored
  24. 2026-10-10 22:59 UTCGHSA enrichmentGHSA-x2wh-r8m8-h3h3 · GitHub severity HIGH · GitHub CVSS 7.3
  25. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  26. 2026-10-10 08:07 UTCEchelonGraph re-scored
  27. 2026-10-10 08:07 UTCGHSA enrichmentGHSA-x2wh-r8m8-h3h3 · GitHub severity HIGH · GitHub CVSS 7.3
  28. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  29. 2026-10-09 19:10 UTCGHSA enrichmentGHSA-x2wh-r8m8-h3h3 · GitHub severity HIGH · GitHub CVSS 7.3
  30. 2026-10-09 05:31 UTCEchelonGraph re-scored
  31. 2026-10-09 05:31 UTCGHSA enrichmentGHSA-x2wh-r8m8-h3h3 · GitHub severity HIGH · GitHub CVSS 7.3
  32. 2026-10-08 17:08 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  33. 2026-10-08 16:33 UTCEchelonGraph re-scored
  34. 2026-10-08 16:33 UTCGHSA enrichmentGHSA-x2wh-r8m8-h3h3 · GitHub severity HIGH · GitHub CVSS 7.3
  35. 2026-10-08 15:38 UTCEchelonGraph re-scored
  36. 2026-10-08 15:38 UTCGHSA enrichmentGHSA-x2wh-r8m8-h3h3 · GitHub severity HIGH · GitHub CVSS 7.3
  37. 2026-10-08 09:04 UTCEchelonGraph re-scored
  38. 2026-10-08 09:04 UTCGHSA enrichmentGHSA-x2wh-r8m8-h3h3 · GitHub severity HIGH · GitHub CVSS 7.3
  39. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  40. 2026-10-07 20:07 UTCGHSA enrichmentGHSA-x2wh-r8m8-h3h3 · GitHub severity HIGH · GitHub CVSS 7.3
  41. 2026-10-07 07:10 UTCGHSA enrichmentGHSA-x2wh-r8m8-h3h3 · GitHub severity HIGH · GitHub CVSS 7.3
  42. 2026-10-06 18:13 UTCEchelonGraph re-scored
  43. 2026-10-06 18:13 UTCGHSA enrichmentGHSA-x2wh-r8m8-h3h3 · GitHub severity HIGH · GitHub CVSS 7.3
  44. 2026-10-06 15:16 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  45. 2026-10-06 05:17 UTCGHSA enrichmentGHSA-x2wh-r8m8-h3h3 · GitHub severity HIGH · GitHub CVSS 7.3
  46. 2026-10-05 16:16 UTCGHSA enrichmentGHSA-x2wh-r8m8-h3h3 · GitHub severity HIGH · GitHub CVSS 7.3
  47. 2026-10-05 03:12 UTCEchelonGraph re-scored
  48. 2026-10-05 03:12 UTCGHSA enrichmentGHSA-x2wh-r8m8-h3h3 · GitHub severity HIGH · GitHub CVSS 7.3
  49. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  50. 2026-10-04 13:59 UTCGHSA enrichmentGHSA-x2wh-r8m8-h3h3 · GitHub severity HIGH · GitHub CVSS 7.3
  51. 2026-10-04 01:02 UTCEchelonGraph re-scored
  52. 2026-10-04 01:02 UTCGHSA enrichmentGHSA-x2wh-r8m8-h3h3 · GitHub severity HIGH · GitHub CVSS 7.3
  53. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  54. 2026-10-03 12:03 UTCGHSA enrichmentGHSA-x2wh-r8m8-h3h3 · GitHub severity HIGH · GitHub CVSS 7.3
  55. 2026-10-02 22:51 UTCEchelonGraph re-scored
  56. 2026-10-02 22:51 UTCGHSA enrichmentGHSA-x2wh-r8m8-h3h3 · GitHub severity HIGH · GitHub CVSS 7.3
  57. 2026-10-02 09:53 UTCGHSA enrichmentGHSA-x2wh-r8m8-h3h3 · GitHub severity HIGH · GitHub CVSS 7.3
  58. 2026-10-01 20:56 UTCEchelonGraph re-scored
  59. 2026-10-01 20:56 UTCGHSA enrichmentGHSA-x2wh-r8m8-h3h3 · GitHub severity HIGH · GitHub CVSS 7.3
  60. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  61. 2026-10-01 07:53 UTCGHSA enrichmentGHSA-x2wh-r8m8-h3h3 · GitHub severity HIGH · GitHub CVSS 7.3
  62. 2026-09-30 18:56 UTCEchelonGraph re-scored
  63. 2026-09-30 18:56 UTCGHSA enrichmentGHSA-x2wh-r8m8-h3h3 · GitHub severity HIGH · GitHub CVSS 7.3
  64. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  65. 2026-09-30 06:00 UTCGHSA enrichmentGHSA-x2wh-r8m8-h3h3 · GitHub severity HIGH · GitHub CVSS 7.3
  66. 2026-09-29 17:03 UTCEchelonGraph re-scored
  67. 2026-09-29 17:03 UTCGHSA enrichmentGHSA-x2wh-r8m8-h3h3 · GitHub severity HIGH · GitHub CVSS 7.3
  68. 2026-09-29 03:34 UTCEchelonGraph re-scored
  69. 2026-09-29 03:34 UTCGHSA enrichmentGHSA-x2wh-r8m8-h3h3 · GitHub severity HIGH · GitHub CVSS 7.3
  70. 2026-09-28 14:31 UTCGHSA enrichmentGHSA-x2wh-r8m8-h3h3 · GitHub severity HIGH · GitHub CVSS 7.3
  71. 2026-09-28 01:27 UTCEchelonGraph re-scored
  72. 2026-09-28 01:27 UTCGHSA enrichmentGHSA-x2wh-r8m8-h3h3 · GitHub severity HIGH · GitHub CVSS 7.3
  73. 2026-09-27 13:44 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile

Frequently asked(5)

What is CVE-2024-58383?
CVE-2024-58383 is a high-severity vulnerability; its CVE record was published on September 14, 2026. Froxlor before 2.2.0 (affected up to and including 2.2.0-rc3) generates /etc/pure-ftpd/db/mysql.conf with mode 0644 via the XML configuration templates in lib/configfiles/, even though the file contains the Froxlor SQL user's password. On systems where the parent directories are world readable (the…
When was CVE-2024-58383 made public?
CVE-2024-58383 was made public on August 23, 2024: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on September 14, 2026. EchelonGraph's copy of the record carries a last-modified date of October 27, 2026; the record at its source may have been updated since.
Is CVE-2024-58383 actively exploited?
CVE-2024-58383 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-58383?
CVE-2024-58383 has a CVSS base score of 7.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2024-58383?
A fix for CVE-2024-58383 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-58383 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-2024-58383

Explore →

Is Your Infrastructure Affected by CVE-2024-58383?

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