CVE-2026-100364 · Package
NO FIX YET · SEE WHAT TO DO
SuiteCRM's V8 JSON:API update path does not strip the record id before assigning user-supplied attributes, so a logged-in user can point an update at another person's record. An attacker can overwrite that record and take ownership of it.
first public Oct 12, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Self-hosted SuiteCRM instances on versions before 7.15.2 or 8.10.2 that expose the V8 JSON:API to users with accounts. The attacker must already have a valid user login. Instances that do not use the V8 API or restrict it to trusted users are at lower risk.
Not affected if api-disabled, auth-required, patched-version
Who cares crm, self-hosted, suitecrm
7.15.28.10.2SuiteCRM is an open-source, enterprise-ready Customer Relationship Management (CRM) software application. Prior to 7.15.2 and 8.10.2, the V8 JSON:API update path fails to remove the id attribute before assigning user-supplied attributes to a SugarBean. The affected flow begins at updateRecord() and uses processAttributes(), id, and ACL_ALLOW_OWNER to carry attacker-controlled data or authorization state into the security-sensitive operation. An authenticated user can substitute a victim record identifier, bypass owner-only authorization, overwrite another record, and hijack record ownership. This issue is fixed in versions 7.15.2 and 8.10.2.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.