Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unrated

Ibexa DXP Download route allows filename change

GHSA-g95c-xc83-8353

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (ibexa/core 4.5.4), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Packagist ibexa/core

    Affected
    >= 4.5.0, < 4.5.4
    Fixed in
    4.5.4

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

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

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-g95c-xc83-8353

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-g95c-xc83-8353

Advisory: Ibexa DXP Download route allows filename change
IDs: GHSA-g95c-xc83-8353
Record: https://patchnext.com/advisories/ghsa-g95c-xc83-8353 (revision 1, source checked 26 Oct 2026, 14:10 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: ibexa/core 4.5.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist ibexa/core: affected >= 4.5.0, < 4.5.4; fixed in 4.5.4

## Suggested inspection (read-only)
- Packagist ibexa/core: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on ibexa/core.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-g95c-xc83-8353 (GitHub-reviewed advisory GHSA-g95c-xc83-8353 lists affected ranges: Packagist ibexa/core >=4.5.0 <4.5.4)

Commands are suggestions: review each one before running it.

Loading voting…