Track vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
7.3

CVE-2026-53911: Cerebrate lets logged‑in users overwrite unrelated records

CVE-2026-53911 · published 4 months ago
Summary

In versions of Cerebrate before 1.37, a user who is signed in could change the identifier of a record in a request and cause the system to update a different record instead of the one intended. This can affect items like users, roles, settings, tools and permissions, potentially letting someone modify data they should not control. Upgrade to Cerebrate 1.37 or later, which blocks the identifier field from being changed, to stop this behavior.

Original advisory text
Cerebrate primary key mass assignment in CRUD edit operations allows authenticated users to overwrite unrelated records
Cerebrate before version 1.37 allowed the id primary key field to be supplied through request input during CRUD edit operations and certain custom entity patching flows. In affected entities that did not explicitly mark id as inaccessible, an authenticated attacker could submit a crafted edit request containing the id of another record, causing the save operation to update that unrelated record instead of the record identified by the route parameter. The issue affected several entity types inheriting permissive mass-assignment defaults, including User, Role, UserSetting, LocalTool, PermissionLimitation, and EnumerationCollection. Since UserSettings edit functionality was reachable by any authenticated user, exploitation could allow unauthorized modification of records within the same entity type, with impact depending on the affected endpoint and writable fields. Cerebrate 1.37 fixes this by stripping id from request input after marshalling callbacks and by globally marking id as inaccessible in the base AppModel entity.

The discovery of those potential vulnerabilities are inherited from initial finding from Jeroen Pinoy additional support from AI-Assisted Optus 4.8 (the commit wrongly assign Claude Fable 5 as the model switched) and coordinated by Andras Iklody.
Fix within
Internet-facing 14 days
Internal 60 days
  • Not known to be exploited
  • Can be exploited automatically
  • Gives an attacker partial control
Severity
7.3 High
Exploitation
<1% chance of attack within 30 days
Type
CWE-639Authorization Bypass Through User-Controlled Key
Timeline
Published11 Jun 2026
Updated29 Oct 2026
First seen11 Jun 2026
Sources
Track software like this
Free during beta