SuiteCRM: SQL injection via id param in modules/Campaigns/PopupCampaignRoi.php
Affects SuiteCRM before 7.15.2 and 8.0.0 through 8.10.1, in the Campaigns module. CVSS score 8.3; no vendor severity rating is given. 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 attacker needs access to the Campaigns module The attacker must prepend an XSS payload to the injection string so the escaping protection is bypassed
- 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? →
- 16/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 campaign ROI popup page that lets a logged-in user with access to Campaigns read arbitrary database tables through time-based blind injection. The attack can be launched remotely over the network, but it requires a valid login.
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, modules/Campaigns/PopupCampaignRoi.php interpolates $_REQUEST['id'] into SQL. Although securexss() normally entity-encodes quotes, an input prefixed with an XSS payload makes AntiXSS select a processed string instead of the entity-encoded backup, allowing a literal quote to reach the query. An authenticated user with Campaigns access can perform time-based blind SQL injection against arbitrary database tables. 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.3/10CVSS 8.3
- No patch0/5No signal
What would change the score
- Would score about 66 if added to CISA KEV
- Would score about 61 if CISA's SSVC rates exploitation active
- Would score about 23 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
The attacker needs access to the Campaigns module The attacker must prepend an XSS payload to the injection string so the escaping protection is bypassedUpgrade 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-61653
Is CVE-2026-61653 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 id parameter in the Campaigns ROI popup is not properly protected, so a crafted value can change the database query that SuiteCRM runs. The flaw can be used to pull sensitive data from any database table using time-based blind SQL injection. The advisory says the existing escaping protection can be bypassed by prepending an XSS payload to the injection string.Source: github.com
Which versions are affected by CVE-2026-61653?
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 releases before 7.15.2 and the 8.x releases from 8.0.0 through 8.10.1 are affected. To check a installation, compare the installed SuiteCRM version against these ranges. The attacker needs access to the Campaigns module.Source: github.com
How do I fix CVE-2026-61653?
Upgrade to SuiteCRM 7.15.2 or to 8.10.2 or later, depending on the release line in use.Source: github.com