CVE-2026-29096
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSuiteCRM 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceSecond-order SQL injection in SuiteCRM's AOR_Reports module where the `field_function` POST parameter is stored unsanitized in the `aor_fields` table and later concatenated into SQL queries without sanitization when reports are executed. Authenticated users with Reports access can exploit this to extract database contents; MySQL with FILE privilege enables RCE via SELECT INTO OUTFILE.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 7.15.1>= 8.0.0, < 8.9.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check SuiteCRM versionLocate the version file (typically at include/SuiteCRM/Version.php for v7 or composer.json in the root for v8) or access the About page in the admin panel to identify the installed version number.Affected if The installed version is less than 7.15.1, or greater than or equal to 8.0.0 but less than 8.9.3.
-
Verify AOR_Reports module accessLog in as an authenticated user and navigate to the Reports module (AOR_Reports). Confirm the module is accessible and not disabled in Admin > Module Loader > Module Management.Affected if The AOR_Reports module is installed, enabled, and accessible to the user account being tested.
-
Inspect aor_fields table for unsanitized dataQuery the database table 'aor_fields' (e.g., SELECT id, field, field_function FROM aor_fields WHERE field_function IS NOT NULL) to examine stored values in the field_function column.Affected if The field_function column contains SQL fragments, special characters, or values not matching expected function names (e.g., raw SQL operators or concatenated strings).
-
Check MySQL user FILE privilegeRun SHOW GRANTS FOR 'your_user'@'host'; or SELECT * FROM mysql.user WHERE User='your_user' AND File_priv='Y'; to determine if the database user has the FILE privilege.Affected if The database user connecting to SuiteCRM has the FILE privilege granted, which combined with the SQL injection could enable RCE via SELECT INTO OUTFILE.
The environment is affected if SuiteCRM version is within the vulnerable range AND the AOR_Reports module is accessible to users, with potential evidence of exploitation visible in the aor_fields table.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped7.15.18.9.3
Upgrade to SuiteCRM version 7.15.1 or 8.9.3 to patch the vulnerability. If immediate upgrade is not possible, restrict Reports module access to trusted users only.
SuiteCRM 7.15.1+ (for 7.x branch) or SuiteCRM 8.9.3+ (for 8.x branch)
- 1. Create a complete backup of your SuiteCRM database and files
- 2. Identify your current SuiteCRM version (7.x or 8.x) to determine the correct upgrade path
- 3. Download SuiteCRM version 7.15.1 (for 7.x installations) or 8.9.3 (for 8.x installations) from the official SuiteCRM repository
- 4. Review the official upgrade documentation at docs.suitecrm.com for your specific version upgrade path
- 5. Execute the upgrade following the standard SuiteCRM upgrade procedure (upload upgrade package, run upgrade wizard)
- 6. Clear all caches (including opcache if used) after upgrade
- 7. Verify the upgrade was successful by checking the About page shows the correct version
- 8. Log in and test the Reports module (AOR_Reports) to confirm functionality works correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-29096 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-29096 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data