Quick answers
- Is CVE-2026-38739 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-38739 being exploited in the wild.
- How severe is CVE-2026-38739?
- High severity, with a CVSS score of 7.1, published 29 May 2026.
- Which products and versions are affected?
- ezsystems/ezpublish-legacy (Packagist) = 2019.03.
- Is there a fix for CVE-2026-38739?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-38739 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-38739?
- Check whether you run eZ Systems eZ Publish Legacy or ezsystems/ezpublish-legacy (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A union-based SQL injection vulnerability exists in eZ Publish Legacy within the dfscleanup.php script and the _getFileList function of the eZDFSFileHandlerMySQLiBackend class. The root cause is improper neutralization of special elements used in SQL commands (CWE-89). An attacker with local shell access and sufficient privileges to execute the cleanup script can manipulate database queries to extract sensitive data. This affects version 2019.03 and potentially other legacy branches. No patches are available as the product has reached end-of-life.
Affected products
- ezsystems ezpublish-legacy 2019.03
Identifiers
- CVE-2026-38739
- GHSA-xg9x-h37w-h3r3
Timeline
- 2026-05-29: advisory: GitHub Advisory GHSA-xg9x-h37w-h3r3 published