CVE-2022-48367
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 · uneditedAn issue was discovered in eZ Publish Ibexa Kernel before 7.5.28. Access control based on object state is mishandled.
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 confidenceeZ Publish Ibexa Kernel before 7.5.28 has a critical access control vulnerability where object state-based authorization checks are incorrectly implemented, potentially allowing unauthorized users to access or modify content they should not have permissions for.
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>= 3.3.0, < 3.3.18>= 4.0.0, < 4.0.5>= 4.1.0, < 4.1.2>= 1.1.0, < 1.1.9>= 2.0.0, < 2.0.11>= 4.0.0, < 4.0.5>= 4.1.0, < 4.1.2>= 1.3.0, < 1.3.17>= 7.5.0, < 7.5.28>= 4.0.0, < 4.0.7>= 4.1.0, < 4.1.4CVSS 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 installed Ibexa Kernel versionRun composer show ibexa/kernel or check the composer.lock file for the ibexa/kernel package versionAffected if The version listed is within any of these ranges: >= 4.0.0 and < 4.0.7; >= 4.1.0 and < 4.1.4; >= 7.5.0 and < 7.5.28; >= 1.3.0 and < 1.3.17
-
Identify installed Ibexa DXP versionRun composer show ibexa/dxp or check composer.json for the ibexa/dxp package versionAffected if The version is within: >= 3.3.0 and < 3.3.18; >= 4.0.0 and < 4.0.5; >= 4.1.0 and < 4.1.2
-
Identify installed Ibexa Fastly cache package versionRun composer show ibexa/fastly or ibexa/ezplatform-http-cache-fastly and note the versionAffected if The version is within: >= 1.1.0 and < 1.1.9; >= 2.0.0 and < 2.0.11; >= 4.0.0 and < 4.0.5; >= 4.1.0 and < 4.1.2
-
Verify object state functionality is in useCheck if the Ibexa installation uses object states by reviewing the content model in the admin interface or via the API for any ContentType or content objects that utilize the ObjectState serviceAffected if Object states are defined and assigned to content items, as the vulnerability specifically affects object state-based authorization checks
You are affected if any Ibexa package version (Kernel, DXP, or Fastly) matches the affected version ranges AND the system uses object state functionality for access control.
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.1.91.3.172.0.11
Upgrade Ibexa Kernel to version 7.5.28 or later to resolve the access control mishandling. Review existing user permissions and access logs for signs of exploitation.
Upgrade to the appropriate fixed version (e.g., 7.5.28 for Ez Platform Kernel 7.5.x, 4.1.4 for Kernel 4.1.x) based on the current product line in use
- 1. Identify the specific product and current version from the affected installations (Digital Experience Platform, Ezplatform Http Cache Fastly, Fastly, Ez Platform Kernel, or Kernel)
- 2. For Digital Experience Platform 3.3.x: upgrade to version 3.3.18
- 3. For Digital Experience Platform 4.0.x: upgrade to version 4.0.5
- 4. For Digital Experience Platform 4.1.x: upgrade to version 4.1.2
- 5. For Ezplatform Http Cache Fastly 1.1.x: upgrade to version 1.1.9
- 6. For Ezplatform Http Cache Fastly 2.0.x: upgrade to version 2.0.11
- 7. For Fastly 4.0.x: upgrade to version 4.0.5
- 8. For Fastly 4.1.x: upgrade to version 4.1.2
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing8.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,472.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-48367 — 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-48367 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