CVE-2026-38739

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-05-29. the CNA's CVSS baseline 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:github_m, epss, ghsa
7.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.1Exploit: NoneExposed: 0

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

ezsystems/ezpublish-legacy has a SQL injection in dfscleanup

NB: All tags and branches in this repository are past their end of life, so the vulnerability will not be fixed. The advisory is posted on the request of the researcher, for the information of anyone who might still use this software.

Impact

There is a security vulnerability in eZ Publish Legacy, affecting the dfscleanup.php script and the _getFileList function of the eZDFSFileHandlerMySQLiBackend class (kernel/private/classes/clusterfilehandlers/dfsbackends/mysqli.php). The vulnerability allows an attacker with local shell access and sufficient privileges to run dfscleanup.php to perform a union-based SQL injection against the eZ Publish MySQL database, potentially exposing sensitive data such as user credentials.

It is known to affect the branch 2019.03, and it may well affect other branches.

Credit

The issue was found and reported by security auditor Timothé Ridel from Advens: https://www.advens.com/

Patches

None, the software is past its end of life.

Workarounds

None.

Resources

  • Report by Advens: https://github.com/Goaterino/ezpublish-legacy-lab/blob/main/SQL%20injection%20and%20arbitrary%20file%20deletion%20in%20dfscleanup.md

CVSS v3
7.1
EG Score
7.1(medium)
EG Risk
36(Track)
EG Risk 36/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
Severity71% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
4.4%
KEV
Not listed

Published

May 29, 2026

Last Modified

May 29, 2026

Vendor Advisories for CVE-2026-38739(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 / EcosystemFixed in / PatchReleasedSource
composerezsystems/ezpublish-legacy—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 rangeFixed inDependents
ezsystems/ezpublish-legacy2019.03——

Weakness Classification(1)

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

Data Freshness Timeline

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-38739?
CVE-2026-38739 is a high vulnerability published on May 29, 2026. ezsystems/ezpublish-legacy has a SQL injection in dfscleanup NB: All tags and branches in this repository are past their end of life, so the vulnerability will not be fixed. The advisory is posted on the request of the researcher, for the information of anyone who might still use this software.…
When was CVE-2026-38739 disclosed?
CVE-2026-38739 was first published in the National Vulnerability Database on May 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-38739 actively exploited?
CVE-2026-38739 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 4.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-38739?
CVE-2026-38739 has a CVSS v4.0 base score of 7.1 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-38739?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-38739, 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-2026-38739

Explore →

Is Your Infrastructure Affected by CVE-2026-38739?

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

Start Free Scan →Browse All CVEs