CVE-2022-25336
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 Insecure Direct Object Reference (IDOR) attacks against image files because the image path and filename can be correctly deduced.
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 · high confidenceIbexa DXP ezsystems/ezpublish-kernel versions 7.5.x before 7.5.26 and 1.3.x before 1.3.12 contains an IDOR vulnerability allowing unauthorized access to image files. Attackers can deduce image paths and filenames to access files without proper authorization checks.
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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
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 if ezpublish-kernel is installedCheck your application's composer.json or the installed packages list for the 'ezsystems/ezpublish-kernel' packageAffected if The package is present in the vendor directory or declared in composer.json
-
Determine the installed versionRun 'composer show ezsystems/ezpublish-kernel' or inspect the version in your composer.lock fileAffected if The installed version is 1.3.x before 1.3.12, or 7.5.x before 7.5.26
-
Confirm the product is Ibexa DXP or eZ PlatformVerify the application is built on Ibexa DXP (formerly eZ Platform) by checking the main configuration or vendor packagesAffected if The application uses Ibexa DXP or eZ Platform with the vulnerable kernel version
-
Check if image/FileService is accessibleInspect the image handling configuration and verify if the FileService or image preview functionality is enabled and publicly accessibleAffected if Image files can be accessed via URL patterns that could reveal file paths or IDs without authorization checks
You are affected if ezsystems/ezpublish-kernel version 1.3.x below 1.3.12 or 7.5.x below 7.5.26 is installed and image files are accessible through the system.
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 to ezsystems/ezpublish-kernel 7.5.26, 1.3.12, or later versions which contain the fix for this IDOR vulnerability.
Ez Platform Kernel 1.3.12 or 7.5.26
- Identify the current version of ezsystems/ezpublish-kernel in your composer.json
- Run composer require ezsystems/ezpublish-kernel:1.3.12 (for 1.3.x branch) or ezsystems/ezpublish-kernel:7.5.26 (for 7.5.x branch) to update to the patched version
- Run composer update to apply the changes
- Clear the application cache (e.g., php bin/console cache:clear)
- Verify the version has been updated by checking composer.lock or running composer show ezsystems/ezpublish-kernel
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-25336 — 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-25336 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