How severe is GHSA-3g43-xfrw-pv5m?

No CVSS score has been assigned to GHSA-3g43-xfrw-pv5m yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-3g43-xfrw-pv5m?

GHSA-3g43-xfrw-pv5m affects the following packages: ezsystems/repository-forms (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-3g43-xfrw-pv5m?

Update ezsystems/repository-forms to 2.3.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3g43-xfrw-pv5m is resolved across your whole dependency graph.

How do I detect GHSA-3g43-xfrw-pv5m in my Packagist dependencies?

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

How do I mitigate GHSA-3g43-xfrw-pv5m if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-3g43-xfrw-pv5m?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-3g43-xfrw-pv5m can be triaged on real exposure rather than presence alone.

Is GHSA-3g43-xfrw-pv5m actively exploited in the wild?

No public exploit code has been indexed for GHSA-3g43-xfrw-pv5m 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-3g43-xfrw-pv5m published, and has it been updated?

GHSA-3g43-xfrw-pv5m was published on May 15, 2024 and was last updated on November 29, 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

GHSA-3g43-xfrw-pv5m — ezsystems/repository-forms

Fix: ezsystems/repository-forms@ea82e13

GHSA-3g43-xfrw-pv5m is a security vulnerability in ezsystems/repository-forms. A fix is available for ezsystems/repository-forms — see the affected versions and patch details below.

eZ Platform User data disclosure

Published

May 15, 2024

Updated

Nov 29, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 29, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐘ezsystems/repository-forms

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

To install, use Composer to update "ezsystems/repository-forms" to the "Resolving versions" mentioned above, or apply this patch manually: https://github.com/ezsystems/repository-forms/commit/ea82e136ec1ea40aca714abb79cc8e5bfece01e8

Have you found a security bug in eZ Publish or eZ Platform? See how to report it responsibly here: https://doc.ez.no/Security

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`ezsystems/repository-forms`	≥ 2.3.0&&< 2.3.2.1	2.3.2.1`composer require ezsystems/repository-forms:^2.3.2.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ezsystems/repository-forms, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ezsystems/repository-forms to 2.3.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3g43-xfrw-pv5m is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-3g43-xfrw-pv5m can be triaged on real exposure rather than presence alone.

Tailored to GHSA-3g43-xfrw-pv5m. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

In eZ Platform v2.3.x it is possible to bypass permission checks in a particular case. This means user data such as name and email (but not passwords or password hashes) can be read by unauthenticated users. This affects only v2.3.x. If you use v2.2.x or older you are not affected. To install, use Composer to update "ezsystems/repository-forms" to the "Resolving versions" mentioned above, or apply this patch manually: https://github.com/ezsystems/repository-forms/commit/ea82e136ec1ea40aca714abb79cc8e5bfece01e8 Have you found a security bug in eZ Publish or eZ Platform? See how to report it r

O3 Security · Impact-Aware SCA

Is GHSA-3g43-xfrw-pv5m in your dependencies?

O3 Security finds GHSA-3g43-xfrw-pv5m across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works