Is CVE-2026-69140 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-69140 being exploited in the wild.

How severe is CVE-2026-69140?

High severity, with a CVSS score of 8.3, published 5 November 2026.

Which products and versions are affected?

SuiteCRM Before 7.15.2 and 8.10.2.

Is there a fix for CVE-2026-69140?

Yes: fixed in 7.15.2, 8.10.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-69140 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-69140?

Check whether you run SuiteCRM at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-69140: SuiteCRM SQL injection in GetLatestRevision.php

CVE-2026-69140 · Severity: high · CVSS 8.3 · Published 2026-11-05

SuiteCRM is an open-source CRM system used by enterprises to manage customer relationships. A low-privileged user with access to the Documents module can exploit improper input validation in a PHP script to inject SQL commands, allowing them to read sensitive database information and modify linked document records without authorization.

Technologies: SuiteCRM. Vendors: SuiteCRM.

Quick answers

Is CVE-2026-69140 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-69140 being exploited in the wild.
How severe is CVE-2026-69140?: High severity, with a CVSS score of 8.3, published 5 November 2026.
Which products and versions are affected?: SuiteCRM Before 7.15.2 and 8.10.2.
Is there a fix for CVE-2026-69140?: Yes: fixed in 7.15.2, 8.10.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-69140 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-69140?: Check whether you run SuiteCRM at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: 7.15.2, 8.10.2

Technical details

GetLatestRevision.php fails to properly sanitize the get_latest_for_id parameter before interpolating it into an SQL UPDATE statement. An attacker can bypass the securexss() encoding function by prefixing input with an XSS payload, causing AntiXSS to select an unencoded string that includes a literal quote character. This allows SQL injection for READ and UPDATE operations; stacked queries and destructive operations (DROP, INSERT) are blocked by the database driver.

Affected products

SuiteCRM SuiteCRM Before 7.15.2 and 8.10.2

Timeline

2026-11-05: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.