SuiteCRM: SQL injection via parameter_value[0] param in AOR_Report.php
SuiteCRM versions before 7.15.2 and from 8.0.0 before 8.10.2 are affected when a report condition is user-controllable (parameter = 1) with type Multi. 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. A report condition is configured as user-controllable (parameter = 1) with type Multi
- 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, has an SQL injection flaw in its AOR Reports feature that lets a remote attacker with a low-privilege login read arbitrary database tables and tie up database connections with delay expressions. The attacker reaches it over the network with an ordinary account that has AOR Reports access, and no user action is needed.
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, a user-controllable Multi report condition passes parameter_value through unencodeMultienum() and concatenates the result into a SQL WHERE clause. Although securexss() normally entity-encodes quotes, an input prefixed with an XSS payload makes AntiXSS select a processed string instead of the encoded backup, allowing a literal quote to reach the database. A low-privileged user with AOR Reports access can read arbitrary tables through time-based or UNION-based SQL injection and can consume database connections with delay expressions. 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.
A report condition is configured as user-controllable (parameter = 1) with type MultiUpgrade 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-61648
Is CVE-2026-61648 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 parameter_value[0] input in AOR_Report.php is used in a database query without proper sanitization, which allows SQL injection. An authenticated low-privilege user with AOR Reports access can read any database table through time-based blind or UNION-based injection, and can cause sustained response delays with SLEEP payloads.Source: github.com
Which versions are affected by CVE-2026-61648?
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?
Affected versions are those before 7.15.2 and those from 8.0.0 before 8.10.2. The affected setup requires a report condition configured as user-controllable (parameter = 1) with type Multi. Compare the installed SuiteCRM version against these ranges and review AOR Reports conditions for parameter = 1 with type Multi.Source: github.com
How do I fix CVE-2026-61648?
Upgrade to SuiteCRM 7.15.2 or 8.10.2, matching the release line in use.Source: github.com