CVE-2022-25337
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIbexa DXP ezsystems/ezpublish-kernel 7.5.x before 7.5.26 and 1.3.x before 1.3.12 allows injection attacks via image filenames.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceIbexa DXP (formerly eZ Publish) ezsystems/ezpublish-kernel versions 7.5.x before 7.5.26 and 1.3.x before 1.3.12 contains an injection vulnerability in image filename handling. The critical CVSS score of 9.8 indicates this is easily exploitable and allows attackers to inject malicious payloads through uploaded image filenames.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 1.3.0, < 1.3.12>= 7.5.0, < 7.5.26CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify ezpublish-kernel package versionRun 'composer show ezsystems/ezpublish-kernel' to display the installed version of the kernel packageAffected if The version is less than 1.3.12 (for 1.3.x branch) or less than 7.5.26 (for 7.5.x branch)
-
Confirm Ibexa DXP installationCheck your project's composer.json for dependency on ezsystems/ezpublish-kernel or ezplatform-kernelAffected if The package is present with a version matching the affected ranges
-
Verify image upload functionality is in useReview application configuration files for image-related IO handlers, image field types, or media locations that accept user-uploaded imagesAffected if The application accepts image uploads through content fields, media library, or REST API
-
Inspect image filename processing settingsExamine configuration under ezplatform.yml, ezsettings, or equivalent for image filename transformation or variation handlersAffected if Custom filename handlers or non-default image processing pipelines are configured
You are affected if your installed ezpublish-kernel version falls within 1.3.0 to 1.3.11 or 7.5.0 to 7.5.25 and the system accepts user-uploaded images through Ibexa DXP content fields or media features.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.3.127.5.26
Upgrade ezsystems/ezpublish-kernel to version 7.5.26 or 1.3.12 or later. Implement filename sanitization for all uploaded images in the interim.
Upgrade to ezsystems/ezpublish-kernel 1.3.12 or 7.5.26 (or later)
- Update your composer.json to require ezsystems/ezpublish-kernel version 1.3.12 or later (for 1.3.x line) or 7.5.26 or later (for 7.5.x line)
- Run `composer update ezsystems/ezpublish-kernel` to install the patched version
- Clear any caches (e.g., `php bin/console cache:clear` or `php bin/console ezplatform:cache:clear`)
- Verify the upgrade was successful by checking the installed version with `composer show ezsystems/ezpublish-kernel`
- Test your application's image upload and processing functionality to confirm the vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-25337 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-25337 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data