# CVE-2022-48367: Object state limitation has no effect

> Attackers can bypass access controls based on object state in Ibexa Kernel, potentially accessing unauthorized content.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Mar 2023
- **Updated:** 4 Mar 2025
- **Also known as:** GHSA-5x4f-7xgq-r42x, GHSA-h5v2-wrhp-5v35

## What is CVE-2022-48367?

CVE-2022-48367 is a critical missing authorization vulnerability in n/a, published on 12 Mar 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in eZ Publish Ibexa Kernel before 7.5.28. Access control based on object state is mishandled.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2022-48367?

4 open source packages ship an affected version, including ezsystems/ezpublish-kernel. It affects 5 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ezsystems/ezpublish-kernel` | Packagist | From 7.5.0 | 7.5.28 |
| `ezsystems/ezpublish-kernel` | Packagist | From 7.5.0 | 7.5.28 |
| `ezsystems/ezpublish-kernel` | Packagist | From 7.5.0 | 7.5.28 |
| `ezsystems/ezpublish-kernel` | Packagist | From 7.5.0 | 7.5.28 |

Products: Ibexa Digital Experience Platform, Ibexa Ez Platform Kernel, Ibexa Ezplatform-Http-Cache-Fastly, Ibexa Fastly, Ibexa Kernel.

## How do I fix CVE-2022-48367?

Upgrade ezsystems/ezpublish-kernel to 7.5.28 or later.

## Is CVE-2022-48367 being exploited?

There is no known exploitation of CVE-2022-48367 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2022-48365](https://insights.sbomify.com/CVE-2022-48365/): Company admin role gives excessive privileges in eZ Platform Ibexa (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-48367 and fix it if it is affected.

What it is: CVE-2022-48367 is a critical missing authorization vulnerability in n/a, published on 12 Mar 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-48367 in the wild and no public exploit code.

Affected packages and fixed versions:
- ezsystems/ezpublish-kernel (Packagist): affected from 7.5.0; fixed in 7.5.28
- ezsystems/ezpublish-kernel (Packagist): affected from 7.5.0; fixed in 7.5.28
- ezsystems/ezpublish-kernel (Packagist): affected from 7.5.0; fixed in 7.5.28
- ezsystems/ezpublish-kernel (Packagist): affected from 7.5.0; fixed in 7.5.28

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-48367/ (Markdown: https://insights.sbomify.com/CVE-2022-48367/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-48367
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-48367
- OSV: https://osv.dev/vulnerability/CVE-2022-48367

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-48367/
Summaries are generated and may contain mistakes; the official description above is the record.