Quick answers
- Is CVE-2026-61648 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-61648 being exploited in the wild.
- How severe is CVE-2026-61648?
- High severity, with a CVSS score of 8.3, published 5 November 2026.
- Which products and versions are affected?
- SuiteCRM prior to 7.15.2 and 8.10.2.
- Is there a fix for CVE-2026-61648?
- Yes: fixed in 7.15.2, 8.10.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-61648 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-61648?
- Check whether you run SuiteCRM at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 7.15.2, 8.10.2
Technical details
The vulnerability exists in the Multi report condition functionality where user-controllable parameter_value input is processed through unencodeMultienum() and concatenated into a SQL WHERE clause. An attacker can exploit a flaw in the AntiXSS input sanitization logic by prefixing an XSS payload that causes the library to use an unencoded string instead of its encoded backup, allowing literal quotes to pass through to the SQL query. This enables time-based or UNION-based SQL injection attacks that allow arbitrary database reads and connection exhaustion via delay expressions.
Affected products
- SuiteCRM SuiteCRM prior to 7.15.2 and 8.10.2
Timeline
- 2026-11-05: advisory