Quick answers
- Is CVE-2026-34372 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-34372 being exploited in the wild.
- How severe is CVE-2026-34372?
- Medium severity, with a CVSS score of 4, published 31 March 2026.
- Which products and versions are affected?
- sulu/sulu (Packagist) ECOSYSTEM:introduced=1.0.0,fixed=2.6.22; Sulu 1.0.0 to < 2.6.22, 3.0.0 to < 3.0.5.
- Is there a fix for CVE-2026-34372?
- Yes. sulu/sulu (Packagist): upgrade to 2.6.22 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-34372 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-34372?
- Check whether you run sulu/sulu (Packagist) or Sulu at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- sulu/sulu (Packagist): upgrade to 2.6.22 or later
composer require sulu/sulu:^2.6.22
Technical details
An authentication bypass (CWE-288) exists in Sulu CMS versions 1.0.0 through 2.6.21 and 3.0.0 through 3.0.4. The vulnerability is located in the admin API endpoints responsible for contact sub-entities. While the system requires a user to have at least one administrative role, it fails to properly verify specific permissions for contact data when accessed through these alternate API paths. An authenticated attacker with low-level admin access can exploit this to retrieve contact information. The issue is resolved in versions 2.6.22 and 3.0.5.
Affected products
- Sulu Sulu 1.0.0 to < 2.6.22, 3.0.0 to < 3.0.5
Identifiers
- CVE-2026-34372
- GHSA-6h7h-m7p5-hjqp
Timeline
- 2026-03-27: patched: Versions 2.6.22 and 3.0.5 released
- 2026-03-31: disclosed: Public advisory published