Cross-tenant data tampering via unchecked object ownership
Published Jul 20, 2026 · Updated Jul 20, 2026
Broken object authorization in NextCRM before 0.12.0 allows remote authenticated users to modify other tenants' contacts and targets. The PATCH handlers for CRM contact and target IDs check only for a session, then update records by URL-supplied ID without matching ownership, assignment, creator, or tenant fields to the session user. A standard member account and another tenant's object UUID are sufficient to overwrite stored CRM data, including contact details and social links.
Summary
What happened
Broken object authorization in NextCRM before 0.12.0 allows remote authenticated users to modify other tenants' contacts and targets. The PATCH handlers for CRM contact and target IDs check only for a session, then update records by URL-supplied ID without matching ownership, assignment, creator, or tenant fields to the session user. A standard member account and another tenant's object UUID are sufficient to overwrite stored CRM data, including contact details and social links.
The record
- CVE
- CVE-2026-47130
- Published
- Jul 20, 2026
- Updated
- Jul 20, 2026
- Vendor
- NextCRM
- Product
- NextCRM
- Classifications
- CWE-639, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 20, 2026CVE publishedPublication date reported by the CVE source.
- Jul 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.12.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GitHub advisory Python PATCH proof of conceptproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo