CVE-2026-71548 · Package
NO FIX YET · SEE WHAT TO DO
SuiteCRM's report builder does not validate a field-type parameter before putting it into a SQL query, so a logged-in user who can save a report can inject SQL. An attacker can read the whole database, including password hashes, OAuth2 tokens and CRM records.
first public Aug 17, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Any SuiteCRM instance before 7.15.2 or 8.10.2 where at least one user can save reports is exposed. The flaw requires a valid login, so instances with only admin-locked or no user accounts are lower risk. Hosted SuiteCRM instances depend on the vendor applying the patch.
Not affected if fixed-version, no-report-editor-users
Who cares crm, php, self-hosted, suitecrm
7.15.2 (7.x line) and before 8.10.2 (8.x line) are affected.7.15.28.10.2SuiteCRM is an open-source, enterprise-ready Customer Relationship Management (CRM) software application. Prior to 7.15.2 and 8.10.2, AOR_Report::build_report_query_where incorporates a report editor's parameter_value when value_type=Field without sufficient validation. An authenticated user who can save a report can use SQL injection to read the entire SuiteCRM database. Disclosed data can include users.user_hash, OAuth2 tokens, CRM records, report definitions, and configuration data; the connector does not permit stacked queries, so direct write-through-injection is not supported. This issue is fixed in versions 7.15.2 and 8.10.2.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.