CVE-2026-54348

HIGHPre-NVD 7.27.2—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7% (49th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
7.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 7.2Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

Froxlor is open source server administration software. Prior to 2.3.8, the Admins.add and Admins.update endpoints in lib/Froxlor/Api/Commands/Admins.php accept an attacker-controlled ipaddress array and store it as JSON in panel_admins.ip without enforcing numeric element types. When the poisoned account later calls IpsAndPorts.listing, lib/Froxlor/Api/Commands/IpsAndPorts.php decodes the array and concatenates its elements into a SQL IN clause without casting or parameterization; the same unsafe pattern is present in lib/Froxlor/Api/Commands/Domains.php. An authenticated administrator with change_serversettings permission can store a UNION-based payload and trigger it through the poisoned account to retrieve arbitrary database data, including administrator login names and bcrypt password hashes, with potential privilege escalation and broader database impact. This issue is fixed in version 2.3.8.

CVSS v3
7.2
EG Score
7.2HIGHmedium confidence
EG Risk
48
EG Risk 48/100CISA SSVC

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
Severity72% × 45%
Exploitation40% × 40%
Automatability0% × 15%
CISA SSVC: Track at low, Track* at medium and Attend at high mission impact.
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.7%
EPSS %ILE
49th
KEV
Not listed

CISA SSVCTrack 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). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 18, 2026

Last Modified

September 8, 2026

Advisory Details (3)

Auto-updated Aug 18, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit, github_release.
github_release Patch Available

froxlor security release 2.3.8

Patch available: froxlor/froxlor 2.3.8

https://github.com/froxlor/froxlor/releases/tag/2.3.8
github_commit Patch Available

commit a1eaca5a1601 (froxlor/froxlor)

Patch available: froxlor/froxlor 2.3.8 (contains commit a1eaca5a1601)

https://github.com/froxlor/froxlor/commit/a1eaca5a1601c8a30e00814a4fc73ad0c185f89e
github Patch Available🟡 PoC Available

Second-Order SQL Injection via `Admins.add` `ipaddress` Parameter Allows Full Database Exfiltration · Advisory · froxlor/froxlor · GitHub

https://github.com/froxlor/froxlor/security/advisories/GHSA-w27m-rmmf-g5w4

Vendor Advisories for CVE-2026-54348(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.3.7 (109 versions)
  • every version up to 2.3.8: fixed in 2.3.8
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 51× 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-10-05 09:37 UTCEG score recompute
  2. 2026-10-04 23:22 UTCEPSS rescore
  3. 2026-10-03 17:37 UTCEG score recompute
  4. 2026-10-03 14:26 UTCEPSS rescore
  5. 2026-10-03 02:51 UTCEG score recompute
  6. 2026-10-02 17:56 UTCEPSS rescore
  7. 2026-10-02 01:25 UTCEG score recompute
  8. 2026-10-01 19:50 UTCEPSS rescore
  9. 2026-09-30 21:38 UTCEG score recompute
  10. 2026-09-30 15:03 UTCEPSS rescore
  11. 2026-09-30 09:47 UTCEG score recompute
  12. 2026-09-29 15:22 UTCEPSS rescore
  13. 2026-09-28 21:55 UTCEG score recompute
  14. 2026-09-28 13:51 UTCEPSS rescore
  15. 2026-09-27 21:12 UTCEG score recompute
  16. 2026-09-27 13:48 UTCEPSS rescore
  17. 2026-09-27 07:54 UTCEG score recompute
  18. 2026-09-26 15:59 UTCEPSS rescore
  19. 2026-09-25 01:24 UTCEG score recompute
  20. 2026-09-24 14:04 UTCEPSS rescore
  21. 2026-09-23 23:30 UTCEG score recompute
  22. 2026-09-23 17:54 UTCEPSS rescore
  23. 2026-09-22 23:47 UTCEG score recompute
  24. 2026-09-21 23:59 UTCEG score recompute
  25. 2026-09-21 00:25 UTCEG score recompute
Show 58 more
  1. 2026-09-20 20:16 UTCEPSS rescore
  2. 2026-09-19 23:44 UTCEG score recompute
  3. 2026-09-18 23:49 UTCEG score recompute
  4. 2026-09-18 19:28 UTCEPSS rescore
  5. 2026-09-18 00:15 UTCEG score recompute
  6. 2026-09-17 19:31 UTCEPSS rescore
  7. 2026-09-16 23:28 UTCEG score recompute
  8. 2026-09-16 14:08 UTCEPSS rescore
  9. 2026-09-16 11:43 UTCEG score recompute
  10. 2026-09-16 05:15 UTCEPSS rescore
  11. 2026-09-15 11:50 UTCEG score recompute
  12. 2026-09-14 00:00 UTCEG score recompute
  13. 2026-09-13 16:47 UTCEPSS rescore
  14. 2026-09-13 00:29 UTCEG score recompute
  15. 2026-09-12 00:59 UTCEG score recompute
  16. 2026-09-11 14:53 UTCEPSS rescore
  17. 2026-09-11 13:13 UTCEG score recompute
  18. 2026-09-10 12:51 UTCEG score recompute
  19. 2026-09-10 09:35 UTCEPSS rescore
  20. 2026-09-09 09:01 UTCEG score recompute
  21. 2026-09-08 22:01 UTCEPSS rescore
  22. 2026-09-07 16:07 UTCEG score recompute
  23. 2026-09-07 16:01 UTCEPSS rescore
  24. 2026-09-06 15:15 UTCEG score recompute
  25. 2026-09-06 13:47 UTCEPSS rescore
  26. 2026-09-05 15:37 UTCEG score recompute
  27. 2026-09-04 15:56 UTCEG score recompute
  28. 2026-09-04 05:06 UTCEPSS rescore
  29. 2026-09-02 16:31 UTCEG score recompute
  30. 2026-09-02 14:12 UTCEPSS rescore
  31. 2026-09-01 14:36 UTCEG score recompute
  32. 2026-09-01 13:54 UTCEPSS rescore
  33. 2026-09-01 04:40 UTCEPSS rescore
  34. 2026-08-31 02:47 UTCEG score recompute
  35. 2026-08-30 19:17 UTCEPSS rescore
  36. 2026-08-30 03:16 UTCEG score recompute
  37. 2026-08-30 01:22 UTCEPSS rescore
  38. 2026-08-29 03:45 UTCEG score recompute
  39. 2026-08-28 21:41 UTCEPSS rescore
  40. 2026-08-27 19:20 UTCEG score recompute
  41. 2026-08-27 14:25 UTCEPSS rescore
  42. 2026-08-26 18:13 UTCEG score recompute
  43. 2026-08-26 14:46 UTCEPSS rescore
  44. 2026-08-25 17:28 UTCEG score recompute
  45. 2026-08-25 13:49 UTCEPSS rescore
  46. 2026-08-24 17:57 UTCEG score recompute
  47. 2026-08-23 06:42 UTCEG score recompute
  48. 2026-08-23 00:19 UTCEPSS rescore
  49. 2026-08-22 07:11 UTCEG score recompute
  50. 2026-08-21 23:49 UTCEPSS rescore
  51. 2026-08-21 07:41 UTCEG score recompute
  52. 2026-08-20 22:55 UTCEPSS rescore
  53. 2026-08-19 20:23 UTCEG score recompute
  54. 2026-08-19 19:34 UTCEG score recompute
  55. 2026-08-19 17:04 UTCEPSS rescore
  56. 2026-08-18 21:36 UTCEG score recompute
  57. 2026-08-18 20:20 UTCEG score recompute
  58. 2026-08-18 20:18 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-54348?
CVE-2026-54348 is a high vulnerability published on August 18, 2026. Froxlor is open source server administration software. Prior to 2.3.8, the Admins.add and Admins.update endpoints in lib/Froxlor/Api/Commands/Admins.php accept an attacker-controlled ipaddress array and store it as JSON in paneladmins.ip without enforcing numeric element types. When the poisoned…
When was CVE-2026-54348 disclosed?
CVE-2026-54348 was first published on August 18, 2026, with the most recent update on September 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54348 actively exploited?
CVE-2026-54348 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (49th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-54348?
CVE-2026-54348 has a CVSS base score of 7.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-54348?
A fix for CVE-2026-54348 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-54348 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-2026-54348

Explore →

Is Your Infrastructure Affected by CVE-2026-54348?

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