CVE-2026-29096
Received Received - Intake
Second-Order SQL Injection in SuiteCRM Reports Enables Data Theft

Publication date: 2026-03-19

Last updated on: 2026-03-24

Assigner: GitHub, Inc.

Description
SuiteCRM is an open-source, enterprise-ready Customer Relationship Management (CRM) software application. Prior to versions 7.15.1 and 8.9.3, when creating or editing a report (AOR_Reports module), the `field_function` parameter from POST data is saved directly into the `aor_fields` table without any validation. Later, when the report is executed/viewed, this value is concatenated directly into a SQL SELECT query without sanitization, enabling second-order SQL injection. Any authenticated user with Reports access can extract arbitrary database contents (password hashes, API tokens, config values). On MySQL with FILE privilege, this could lead to RCE via SELECT INTO OUTFILE. Versions 7.15.1 and 8.9.3 patch the issue.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-03-19
Last Modified
2026-03-24
Generated
2026-06-16
AI Q&A
2026-03-20
EPSS Evaluated
2026-06-15
NVD
CVE-2026-29096
Affected Vendors & Products
Showing 2 associated CPEs
Vendor Product Version / Range
suitecrm suitecrm to 7.15.1 (exc)
suitecrm suitecrm From 8.0.0 (inc) to 8.9.3 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-89 The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability exists in SuiteCRM versions prior to 7.15.1 and 8.9.3 within the AOR_Reports module. When creating or editing a report, the `field_function` parameter from POST data is saved directly into the database without any validation. Later, this unsanitized value is concatenated into a SQL SELECT query, enabling a second-order SQL injection attack.

Any authenticated user with access to Reports can exploit this flaw to extract arbitrary database contents such as password hashes, API tokens, and configuration values. On MySQL servers with FILE privileges, this vulnerability could even lead to remote code execution (RCE) via the SELECT INTO OUTFILE command.

The issue is fixed in SuiteCRM versions 7.15.1 and 8.9.3.

Impact Analysis

This vulnerability can have serious impacts including unauthorized access to sensitive data stored in the database such as password hashes, API tokens, and configuration settings.

If the underlying MySQL database has FILE privileges enabled, an attacker could execute arbitrary code on the server, leading to full system compromise.

Because the attack requires only authenticated user access to Reports, it increases the risk from insider threats or compromised user accounts.

Compliance Impact

I don't know

Detection Guidance

I don't know

Mitigation Strategies

To mitigate this vulnerability, you should upgrade SuiteCRM to versions 7.15.1 or 8.9.3 or later, where the issue has been patched.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-29096. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart