SuiteCRM: Admin OS RCE via Dropdown Editor PHP Injection
Affects SuiteCRM releases before 7.15.2 and 8.0.0 through 8.10.1 where the Studio Dropdown Editor is in use. No vendor rating is given. Fixed in 7.15.2 and 8.10.2.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- 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. Studio Dropdown Editor feature in use
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 17/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
SuiteCRM, an open-source customer relationship management application, has a flaw in its Studio Dropdown Editor that lets an administrator inject persistent PHP code, which then runs with the web server's privileges and can compromise the application and the host. The flaw can be reached remotely over the network, but the attacker needs high-privilege administrator credentials to do it.
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 Studio Dropdown Editor passes $dropdown_name through html_entity_decode() and writes the result verbatim into a PHP language file under custom/ that is included on later page loads. An administrator can inject persistent PHP that executes as the web-server account, survives cache clears, and compromises application and host confidentiality, integrity, and availability. This issue is fixed in versions 7.15.2 and 8.10.2.
cve.now Index
- 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.4/10CVSS 9.4
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Studio Dropdown Editor feature in useUpgrade to a fixed version: 7.15.2, 8.10.2.
Timeline
- CVE published
- First seen by cve.now1 day
- 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
- Advisory
- Repository
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-100358
Is CVE-2026-100358 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?
An unsafe PHP code injection in the Studio Dropdown Editor lets an administrator inject PHP code that runs on the server as www-data. The advisory describes this as OS-level code execution with full impact on the application and host.Source: github.com
Which versions are affected by CVE-2026-100358?
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 8.0.0 through 8.10.1 are in the affected ranges, and the bug requires the Studio Dropdown Editor feature to be in use. Check the installed SuiteCRM version against these ranges and whether the Studio Dropdown Editor is used.Source: github.com
How do I fix CVE-2026-100358?
Upgrade to SuiteCRM 7.15.2 if on the 7.x line, or to 8.10.2 if on the 8.x line. The facts give no other workaround.Source: github.com