SuiteCRM: SQL Injection via REST API securexss() Bypass in Relationship Management
Affects SuiteCRM versions before 7.15.2 and 8.0.0 through 8.10.1 that expose the REST v4 set_relationship method. Fixed in 7.15.2 and 8.10.2.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 7.15.2, 8.10.2
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. The REST v4 API set_relationship method passes relationship field values to SQL INSERT/UPDATE statements
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 17/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
SuiteCRM, an open-source customer relationship management application, contains a SQL injection flaw in its REST API relationship management code that lets a remote attacker with a low-privilege login read or change database data. The attacker can reach it over the network by logging in with a regular user account, and in some cases could also write files if the database account has elevated privileges.
Read the original description
SuiteCRM is an open-source, enterprise-ready Customer Relationship Management (CRM) software application. Prior to 7.15.2 and 8.10.2, the REST v4 JSON handler reads the pre-filter RAW_REQUEST value and relationship write helpers interpolate supplied field values into INSERT and UPDATE statements. The affected flow begins at $GLOBALS['RAW_REQUEST'] and uses set_relationship, SugarRelationship::addRow(), SugarRelationship::updateRow(), and contact_role to carry attacker-controlled data or authorization state into the security-sensitive operation. An authenticated user can inject SQL through relationship fields to read or alter database data and may reach file-write consequences when the database account has elevated privileges. This issue is fixed in versions 7.15.2 and 8.10.2.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.8/10CVSS 8.8
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
The REST v4 API set_relationship method passes relationship field values to SQL INSERT/UPDATE statementsUpgrade to a fixed version: 7.15.2, 8.10.2.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- SuiteCRM SuiteCRM
fixed in 7.15.2; From 8.0.0 · fixed in 8.10.2
Evidence 5
- Advisory
- Repository
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-69134
Is CVE-2026-69134 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The set_relationship method in the REST v4 API passes user-controlled relationship field values into SQL INSERT and UPDATE statements through SugarRelationship::addRow() and updateRow(). This lets crafted input get past the securexss() check and reach the database as SQL, which is an SQL injection flaw.Source: github.com
Which versions are affected by CVE-2026-69134?
SuiteCRM: before 7.15.2; from 8.0.0 before 8.10.2.Source: cve.now feed data
Am I affected, and how do I check?
SuiteCRM versions before 7.15.2, and 8.0.0 up to but not including 8.10.2, are affected when the REST v4 API is in use and the set_relationship method is reachable. To check, look up the installed SuiteCRM version number and compare it with the fixed versions.Source: github.com
How do I fix CVE-2026-69134?
Upgrade to SuiteCRM 7.15.2 if you are on the 7.x line, or to 8.10.2 if you are on the 8.x line. Both are listed as patched versions in the advisory.Source: github.com