Skip to main content
← Vulnerabilities

SuiteCRM: LFI to RCE via AOW_WorkFlow

Affects SuiteCRM before 7.15.2 and 8.0.0 through 8.10.1, for users holding the WorkFlow role (AOW_WorkFlow, Access: Enabled). Fixed in 7.15.2 and 8.10.2.

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

9.9CriticalCNA
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. Authenticated user holding the WorkFlow role (AOW_WorkFlow, Access: Enabled)

Published
Last modified
18/100 · provisional
Specific setups only
None on Exploit-DB, Metasploit or GitHub
On X
View the cve.now post

Summary

SuiteCRM's workflow controller can be reached remotely by an attacker with low-privilege login, who can include attacker-chosen PHP files and run code on the server. This gives the attacker access to CRM data and configuration secrets and lets them maintain persistent access.

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, the workflow controller uses a path-traversal-capable aow_action value in require_once() without constraining the resolved file. The affected flow begins at modules/AOW_WorkFlow/controller.php and uses aow_action, and require_once() to carry attacker-controlled data or authorization state into the security-sensitive operation. An authenticated user with the WorkFlow role can include executable PHP, obtain server-side code execution, access CRM data and configuration secrets, and establish persistent access. 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
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity9.9/10CVSS 9.9
  • 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.

    Authenticated user holding the WorkFlow role (AOW_WorkFlow, Access: Enabled)
  • Upgrade to a fixed version: 7.15.2, 8.10.2.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now

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-71550

Is CVE-2026-71550 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 logged-in user with the WorkFlow role can make the workflow feature execute arbitrary PHP files on the server. The advisory describes this as leading to remote code execution, access to CRM data and config secrets such as database credentials, and filesystem read and write.Source: github.com

Which versions are affected by CVE-2026-71550?

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?

SuiteCRM versions before 7.15.2, and versions from 8.0.0 up to but not including 8.10.2. The bug needs an authenticated session with the WorkFlow role, where AOW_WorkFlow Access is Enabled; check the version in the admin panel and that role's AOW_WorkFlow setting under role management.Source: github.com

How do I fix CVE-2026-71550?

Upgrade to 7.15.2 if on the 7.x line, or to 8.10.2 if on the 8.x line. The facts give no separate workaround.Source: github.com