How severe is GHSA-g95c-xc83-8353?

No CVSS score has been assigned to GHSA-g95c-xc83-8353 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-g95c-xc83-8353?

GHSA-g95c-xc83-8353 affects the following packages: ibexa/core (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-g95c-xc83-8353?

Update ibexa/core to 4.5.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g95c-xc83-8353 is resolved across your whole dependency graph.

How do I detect GHSA-g95c-xc83-8353 in my Packagist dependencies?

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

How do I mitigate GHSA-g95c-xc83-8353 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.

Is GHSA-g95c-xc83-8353 actively exploited in the wild?

No public exploit code has been indexed for GHSA-g95c-xc83-8353 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-g95c-xc83-8353 published, and has it been updated?

GHSA-g95c-xc83-8353 was published on November 3, 2023 and was last updated on December 4, 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

Ibexa DXP Download route allows filename changeGHSA-g95c-xc83-8353

Fix: ibexa/core@704f221

GHSA-g95c-xc83-8353 is a security vulnerability in ibexa/core. A fix is available for ibexa/core — see the affected versions and patch details below.

Published

Nov 3, 2023

Updated

Dec 4, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Real-World Exposure

1 pkg affected

🐘ibexa/core

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

The route used for file downloads allows specifying the name of the downloaded file. This is an unintended side effect of the implementation, and means one could construct download URLs with filenames that have no relation to the actual file, which could lead to misunderstandings and confusion, and possibly other harm. As such it is a low severity vulnerability. It affects all supported versions of Ibexa DXP and eZ Platform, in installations where downloadable files exist.

Patches

The issue is fixed in all supported versions of ibexa/core, see "Patched versions". An advisory is also published for ezsystems/ezpublish-kernel and ezsystems/ezplatform-kernel, please see those repositories. Commit: https://github.com/ibexa/core/commit/704f221031ea4e32bd5510fe4c1fa8e0f664cbd4

Workarounds

None, other than blocking all downloads.

References

https://developers.ibexa.co/security-advisories/ibexa-sa-2023-005-vulnerabilities-in-solr-search-and-file-downloads

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`ibexa/core`	≥ 4.5.0&&< 4.5.4	4.5.4`composer require ibexa/core:^4.5.4`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ibexa/core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ibexa/core to 4.5.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g95c-xc83-8353 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.

Frequently Asked Questions

### Impact The route used for file downloads allows specifying the name of the downloaded file. This is an unintended side effect of the implementation, and means one could construct download URLs with filenames that have no relation to the actual file, which could lead to misunderstandings and confusion, and possibly other harm. As such it is a low severity vulnerability. It affects all supported versions of Ibexa DXP and eZ Platform, in installations where downloadable files exist. ### Patches The issue is fixed in all supported versions of ibexa/core, see "Patched versions". An advisory is

O3 Security · Impact-Aware SCA

Is GHSA-g95c-xc83-8353 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works