Skip to content
Fencer Intel
high —

GHSA-jpwx-ffjq-wr4w json

Content object state fetch functions open to SQL injection

published 5y ago modified last yr.

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

### Impact This Security Update is about a vulnerability in eZ Publish Legacy. The content object state code could be vulnerable to SQL injection. There is no known exploit, but one might be possible. If you use Legacy in any way, we strongly recommend that you install this update as soon as possible.

### Patches The fix is distributed via Composer, see "Patched versions".

Patch / fix

  • packagist ezsystems/ezpublish-legacy 2017.12.7.4, 2019.03.6.1

Is GHSA-jpwx-ffjq-wr4w in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
packagist ezsystems/ezpublish-legacy
>=2018.06.0, <2019.03.6.1
<2017.12.7.4
2019.03.6.1
2017.12.7.4

Classification

Weakness
  • CWE-89 Improper Neutralization of Special Elements used in an SQL Command

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.