# CVE-2026-29096: SuiteCRM vulnerable to Authenticated SQL Injection via unsanitized field_function in Report Fields

> Authenticated users can execute arbitrary SQL queries via unsanitized report fields, potentially extracting sensitive data or achieving remote code execution.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Mar 2026
- **Updated:** 25 Mar 2026
- **Also known as:** GHSA-vh42-gmqm-q55m

## What is CVE-2026-29096?

CVE-2026-29096 is a high-severity SQL injection vulnerability in SuiteCRM, published on 19 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-29096?

It affects 1 product.


Products: Suitecrm Suitecrm.

## How do I fix CVE-2026-29096?

No fix has been published for CVE-2026-29096 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-29096 being exploited?

There is no known exploitation of CVE-2026-29096 in the wild and no public exploit code.

## Other vulnerabilities in SuiteCRM

- [CVE-2026-29103](https://insights.sbomify.com/CVE-2026-29103/): SuiteCRM Vulnerable to Remote Code Execution via Module Loader Package Scanner Bypass (critical 9.1)
- [CVE-2026-29099](https://insights.sbomify.com/CVE-2026-29099/): SuiteCRM has Authenticated Blind SQL Injection in OutboundEmail Legacy Functionality. (high 8.8)
- [CVE-2026-33288](https://insights.sbomify.com/CVE-2026-33288/): SuiteCRM has Authenticated SQL Injection in Authentication Module (high 8.8)
- [CVE-2026-33289](https://insights.sbomify.com/CVE-2026-33289/): SuiterCRM has LDAP Filter Injection in Authentication Module (high 8.8)
- [CVE-2026-29109](https://insights.sbomify.com/CVE-2026-29109/): SuiteCRM Authenticated Remote Code Execution via Unsafe Deserialization in SavedSearch Filter Processing (high 8.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-29096 and fix it if it is affected.

What it is: CVE-2026-29096 is a high-severity SQL injection vulnerability in SuiteCRM, published on 19 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-29096 in the wild and no public exploit code.

Affected product: SuiteCRM. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-29096/ (Markdown: https://insights.sbomify.com/CVE-2026-29096/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-29096
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-29096
- OSV: https://osv.dev/vulnerability/CVE-2026-29096

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-29096/
Summaries are generated and may contain mistakes; the official description above is the record.