IBX-1392: Image filenames sanitization
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (ezsystems/ezpublish-kernel 7.5.26), 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.
Affected packages
Packagist ezsystems/ezpublish-kernel
- Affected
- >= 7.5.0, < 7.5.26
- Fixed in
- 7.5.26
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-44m4-9cjp-j587 lists affected ranges: Packagist ezsystems/ezpublish-kernel >=7.5.0 <7.5.26
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
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.
ezsystems/ezpublish-kernel versions 7.5. before 7.5.26 are vulnerable to certain injection attacks and unauthorized access to some image files.
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-44m4-9cjp-j587
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-44m4-9cjp-j587 Advisory: IBX-1392: Image filenames sanitization IDs: GHSA-44m4-9cjp-j587 Record: https://patchnext.com/advisories/ghsa-44m4-9cjp-j587 (revision 1, source checked 26 Oct 2026, 13:56 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.26. A vendor fix does not mean a deployment is fixed. ## Affected components - Packagist ezsystems/ezpublish-kernel: affected >= 7.5.0, < 7.5.26; fixed in 7.5.26 ## 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-44m4-9cjp-j587 (GitHub-reviewed advisory GHSA-44m4-9cjp-j587 lists affected ranges: Packagist ezsystems/ezpublish-kernel >=7.5.0 <7.5.26) Commands are suggestions: review each one before running it.
Loading voting…