Skip to main content
← Vulnerabilities

SuiteCRM: Time-Based Blind SQL Injection via AOR_Reports ORDER BY Clause Allows Data Exfiltration by Any Authenticated User

Affects SuiteCRM before 7.15.2 and 8.0.0 through 8.10.1 for users with access to AOR_Reports. Fixed in 7.15.2 and 8.10.2.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

8.8HighCNA
Exploited
No known exploitation
Fix
Fixed in 7.15.2, 8.10.2
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. Attacker-controlled field label stored in the aor_fields table is concatenated unsanitized into the ORDER BY clause of an AOR_Reports query.

Published
Last modified
18/100 · provisional
Specific setups only
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: total

Summary

SuiteCRM, an open-source customer relationship management application, is affected by a SQL injection flaw in its AOR Reports feature. A remote attacker with low-privilege login and access to AOR Reports can extract data from the database, including password hashes and arbitrary table contents, and can hold database connections open with expensive queries.

Read the original description

SuiteCRM is an open-source, enterprise-ready Customer Relationship Management (CRM) software application. Prior to 7.15.2 and 8.10.2, AOR report generation concatenates an attacker-controlled stored field label into an ORDER BY clause without an allowlist. The affected flow begins at AOR_Reports and uses aor_fields, ORDER BY, and field label to carry attacker-controlled data or authorization state into the security-sensitive operation. An authenticated user with AOR Reports access can perform time-based extraction of password hashes and arbitrary table data and can hold database connections with expensive expressions. This issue is fixed in versions 7.15.2 and 8.10.2.

cve.now Index

18Pcve.now Index 18 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity9.8/10CVSS 8.8, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 68 if added to CISA KEV
  • Would score about 63 if CISA's SSVC rates exploitation active
  • Would score about 25 if CISA's SSVC rates it automatable

What to do

  • Check whether your setup matches what the bug needs.

    Attacker-controlled field label stored in the aor_fields table is concatenated unsanitized into the ORDER BY clause of an AOR_Reports query.
  • Upgrade to a fixed version: 7.15.2, 8.10.2.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

  4. Record last updated

Affected versions

  • SuiteCRM SuiteCRM

    fixed in 7.15.2; From 8.0.0 · fixed in 8.10.2

Evidence 5

  1. Advisory
  2. Repository
  3. Repository
  4. Repository
  5. Repository

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-100365

Is CVE-2026-100365 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

A field label that an attacker can control is stored in the aor_fields table and later joined unsanitized into the ORDER BY clause of an AOR_Reports query. This allows time-based blind SQL injection, which can read database contents such as password hashes, including for administrator accounts. It can also be used to hold database connections open and cause denial of service.Source: github.com

Which versions are affected by CVE-2026-100365?

SuiteCRM: before 7.15.2; from 8.0.0 before 8.10.2.Source: cve.now feed data

Am I affected, and how do I check?

Affected versions are SuiteCRM before 7.15.2 and SuiteCRM 8.0.0 through 8.10.1. The issue requires an authenticated account with access to AOR_Reports. To check a installation, look up the installed SuiteCRM version in the application's version information.Source: github.com

How do I fix CVE-2026-100365?

Upgrade to SuiteCRM 7.15.2 or 8.10.2, which contain the fix. The sources provided do not list a workaround.Source: github.com