Download route allows filename change in eZpublish kernel

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

No dated EPSS signal available.

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 ezsystems/ezpublish-kernel, see "Patched versions". An advisory is also published for ezsystems/ezplatform-kernel and ibexa/core, please see those repositories. Commit: https://github.com/ezsystems/ezpublish-kernel/commit/142152f9bae4c4835713df0bdfe22bc98d03f9a1 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

Published by the source

3 Nov 2023, 18:45 UTC

Last modified by the source

3 Nov 2023, 18:45 UTC

Source last checked

26 Oct 2026, 14:10 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-946c-f9w6-2c25

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

# Patch Next advisory brief: GHSA-946c-f9w6-2c25

Advisory: Download route allows filename change in eZpublish kernel
IDs: GHSA-946c-f9w6-2c25
Record: https://patchnext.com/advisories/ghsa-946c-f9w6-2c25 (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: ezsystems/ezpublish-kernel 7.5.31. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist ezsystems/ezpublish-kernel: affected >= 7.5.0, < 7.5.31; fixed in 7.5.31

## Suggested inspection (read-only)
- Packagist ezsystems/ezpublish-kernel: 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 ezsystems/ezpublish-kernel.
- 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-946c-f9w6-2c25 (GitHub-reviewed advisory GHSA-946c-f9w6-2c25 lists affected ranges: Packagist ezsystems/ezpublish-kernel >=7.5.0 <7.5.31)

Commands are suggestions: review each one before running it.