Exposure of Resource to Wrong Sphere in ezsystems/ezplatform-kernel

Exploitation

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

CVSS

5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

EPSS

• CVE-2022-25336: 0.71% estimated exploitation activity in the next 30 days; percentile 53.47 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

When image files are uploaded, they are made accessible under a name similar to the original file name. There are two issues with this. Both require access to uploading images in order to exploit them, this limits the impact. The first issue is that certain injection attacks can be possible, since not all possible attack vectors are removed from the original file name. The second issue is that direct access to the images is not access controlled. This is by design, for performance reasons, and documented as such. But it does mean that images not meant to be publicly accessible can be accessed, provided that the image path and filename is correctly deduced and/or guessed, through dictionary attacks and similar.

Published by the source

19 Feb 2022, 00:01 UTC

Last modified by the source

8 Aug 2023, 20:08 UTC

Source last checked

26 Oct 2026, 14:06 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-x8xx-x82q-42q3

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

# Patch Next advisory brief: CVE-2022-25336

Advisory: Exposure of Resource to Wrong Sphere in ezsystems/ezplatform-kernel
IDs: CVE-2022-25336, GHSA-x8xx-x82q-42q3
Record: https://patchnext.com/advisories/cve-2022-25336 (revision 1, source checked 26 Oct 2026, 14:06 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: ezsystems/ezplatform-kernel 1.3.12. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist ezsystems/ezplatform-kernel: affected >= 1.3.0, < 1.3.12; fixed in 1.3.12

## Suggested inspection (read-only)
- Packagist ezsystems/ezplatform-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/ezplatform-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-x8xx-x82q-42q3 (GitHub-reviewed advisory GHSA-x8xx-x82q-42q3 lists affected ranges: Packagist ezsystems/ezplatform-kernel >=1.3.0 <1.3.12)

Commands are suggestions: review each one before running it.