PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-34372 sulu CVE debrief

A vulnerability was found in Sulu, 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 with 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 having permission for contacts. This issue has been patched in versions 2.6.22 and 3.0.5.

Vendor
sulu
Product
Unknown
CVSS
MEDIUM 5.3
CISA KEV
Not listed in stored evidence
Original CVE published
2026-03-31
Original CVE updated
2026-07-24
Advisory published
2026-03-31
Advisory updated
2026-07-24

Who should care

Users of Sulu content management system versions 1.0.0 to before 2.6.22, and 3.0.0 to before 3.0.5 who have administrative access via at least one role should verify if they have applied the necessary patches.

Technical summary

The vulnerability exists in the Sulu Admin API, allowing users with at least one role in the Sulu Admin to access sub-entities of contacts without needing explicit permission for contacts. This access could potentially lead to unauthorized data exposure or manipulation. The issue arises from insufficient permission checks in the API endpoints handling contact sub-entities. Affected product deployments should be reviewed for exposure, and owners should verify and apply patches or mitigations. The vulnerability has been patched in Sulu versions 2.6.22 and 3.0.5.

Defensive priority

Medium priority due to the potential for unauthorized access and data manipulation.

Recommended defensive actions

  • Apply patches: Upgrade to Sulu version 2.6.22 or 3.0.5, whichever is applicable.
  • Review user roles: Ensure that users with administrative access via at least one role are aware of the potential vulnerability and are instructed to report any suspicious activity.
  • Monitor API usage: Regularly monitor the admin API for unusual patterns of access to contact sub-entities.
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
  • Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
  • Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review.

Evidence notes

The CVE record was published on 2026-03-31T21:16:29.840Z and was last modified on 2026-07-24T20:10:00.147Z. The NVD entry is currently Analyzed. Evidence is limited to CVE and NVD entries. Defenders should verify affected scope, apply patches, and monitor for suspicious activity. The issue has been publicly disclosed and patches are available.

Official resources

AI-assisted PatchSiren debrief based on the supplied source corpus. The CVE record was published on 2026-03-31T21:16:29.840Z and has not been modified since then. The NVD entry is currently Analyzed.