How severe is GHSA-jpwx-ffjq-wr4w?

No CVSS score has been assigned to GHSA-jpwx-ffjq-wr4w yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-jpwx-ffjq-wr4w?

GHSA-jpwx-ffjq-wr4w affects the following packages: ezsystems/ezpublish-legacy (Packagist), ezsystems/ezpublish-legacy (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-jpwx-ffjq-wr4w?

Update ezsystems/ezpublish-legacy to 2019.03.6.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jpwx-ffjq-wr4w is resolved across your whole dependency graph.

How do I detect GHSA-jpwx-ffjq-wr4w in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ezsystems/ezpublish-legacy, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-jpwx-ffjq-wr4w if there is no patch (or I can't update yet)?

Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Is GHSA-jpwx-ffjq-wr4w actively exploited in the wild?

No public exploit code has been indexed for GHSA-jpwx-ffjq-wr4w yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-jpwx-ffjq-wr4w published, and has it been updated?

GHSA-jpwx-ffjq-wr4w was published on September 7, 2021 and was last updated on December 2, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

Content object state fetch functions open to SQL injectionGHSA-jpwx-ffjq-wr4w

Fix: ezsystems/ezpublish-legacy@f8e3a97

GHSA-jpwx-ffjq-wr4w is a security vulnerability in ezsystems/ezpublish-legacy. A fix is available for ezsystems/ezpublish-legacy — see the affected versions and patch details below.

Published

Sep 7, 2021

Updated

Dec 2, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Dec 2, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected

🐘ezsystems/ezpublish-legacy🐘ezsystems/ezpublish-legacy

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

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".

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`ezsystems/ezpublish-legacy`	≥ 2018.06.0&&< 2019.03.6.1	2019.03.6.1`composer require ezsystems/ezpublish-legacy:^2019.03.6.1`
🐘Packagist	`ezsystems/ezpublish-legacy`	all versions	2017.12.7.4`composer require ezsystems/ezpublish-legacy:^2017.12.7.4`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ezsystems/ezpublish-legacy, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ezsystems/ezpublish-legacy to 2019.03.6.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jpwx-ffjq-wr4w is resolved across your whole dependency graph.
Workarounds
Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Frequently Asked Questions

### 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".

O3 Security · Impact-Aware SCA

Is GHSA-jpwx-ffjq-wr4w in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works