# CVE-2026-34372: Sulu checks fix permissions for subentities endpoints

> Attackers with admin access can read contact sub-entities without specific contact permissions, requiring a patch to enforce proper authorization checks.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 31 Mar 2026
- **Updated:** 31 Mar 2026
- **Also known as:** GHSA-6h7h-m7p5-hjqp

## What is CVE-2026-34372?

CVE-2026-34372 is a medium-severity missing authorization vulnerability in sulu, published on 31 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Sulu is an open-source PHP content management system based on the Symfony framework. From versions 1.0.0 to before 2.6.22, and 3.0.0 to before 3.0.5, a user which has permission for the Sulu Admin via at least one role could have access to the sub-entities of contacts via the admin API without even have permission for contacts. This issue has been patched in versions 2.6.22 and 3.0.5.

Weakness: CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

## Which versions are affected by CVE-2026-34372?

4 open source packages ship an affected version, including sulu/sulu. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `sulu/sulu` | Packagist | From 1.0.0 | 2.6.22 |
| `sulu/sulu` | Packagist | From 1.0.0 | 2.6.22 |
| `sulu/sulu` | Packagist | From 3.0.0 | 3.0.5 |
| `sulu/sulu` | Packagist | From 3.0.0 | 3.0.5 |

Products: Sulu Sulu.

## How do I fix CVE-2026-34372?

Upgrade sulu/sulu to a fixed version for your release line: 2.6.22 or 3.0.5.

## Is CVE-2026-34372 being exploited?

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

## Other vulnerabilities in sulu

- [CVE-2021-43836](https://insights.sbomify.com/CVE-2021-43836/): PHP file inclusion in the Sulu admin panel (high 8.5)
- [CVE-2021-32737](https://insights.sbomify.com/CVE-2021-32737/): XSS Injection in Media Collection Title was possible (high 8.4)
- [CVE-2021-43835](https://insights.sbomify.com/CVE-2021-43835/): Privilege escalation in the Sulu Admin panel (high 7.2)
- [CVE-2024-27915](https://insights.sbomify.com/CVE-2024-27915/): Sulu grants access to pages regardless of role permissions (medium 6.8)
- [CVE-2021-41169](https://insights.sbomify.com/CVE-2021-41169/): Improper Neutralization HTML tags in sulu/sulu (medium 6.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-34372 and fix it if it is affected.

What it is: CVE-2026-34372 is a medium-severity missing authorization vulnerability in sulu, published on 31 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-34372 in the wild and no public exploit code.

Affected packages and fixed versions:
- sulu/sulu (Packagist): affected from 1.0.0; fixed in 2.6.22
- sulu/sulu (Packagist): affected from 1.0.0; fixed in 2.6.22
- sulu/sulu (Packagist): affected from 3.0.0; fixed in 3.0.5
- sulu/sulu (Packagist): affected from 3.0.0; fixed in 3.0.5

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-2026-34372/ (Markdown: https://insights.sbomify.com/CVE-2026-34372/index.md)
```

## Sources

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

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