# CVE-2026-29103: SuiteCRM Vulnerable to Remote Code Execution via Module Loader Package Scanner Bypass

> Authenticated administrators can execute arbitrary system commands in SuiteCRM by bypassing the Module Loader package scanner via PHP token parsing flaws.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Mar 2026
- **Updated:** 20 Mar 2026
- **Also known as:** GHSA-5jjq-9qch-9rg7

## What is CVE-2026-29103?

CVE-2026-29103 is a critical code injection vulnerability in SuiteCRM, published on 19 Mar 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

SuiteCRM is an open-source, enterprise-ready Customer Relationship Management (CRM) software application. A Critical Remote Code Execution (RCE) vulnerability exists in SuiteCRM 7.15.0 and 8.9.2, allowing authenticated administrators to execute arbitrary system commands. This vulnerability is a direct Patch Bypass of CVE-2024-49774. Although the vendor attempted to fix the issue in version 7.14.5, the underlying flaw in ModuleScanner.php regarding PHP token parsing remains. The scanner incorrectly resets its internal state ($checkFunction flag) when encountering any single-character token (such as =, ., or ;). This allows attackers to hide dangerous function calls (e.g., system(), exec()) using variable assignments or string concatenation, completely evading the MLP security controls. Versions 7.15.1 and 8.9.3 patch the issue.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-358 (Improperly Implemented Security Check for Standard)

## Which versions are affected by CVE-2026-29103?

It affects 1 product.


Products: Suitecrm Suitecrm.

## How do I fix CVE-2026-29103?

No fix has been published for CVE-2026-29103 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-29103 being exploited?

There is no known exploitation of CVE-2026-29103 in the wild and no public exploit code.

## Other vulnerabilities in SuiteCRM

- [CVE-2026-29099](https://insights.sbomify.com/CVE-2026-29099/): SuiteCRM has Authenticated Blind SQL Injection in OutboundEmail Legacy Functionality. (high 8.8)
- [CVE-2026-33288](https://insights.sbomify.com/CVE-2026-33288/): SuiteCRM has Authenticated SQL Injection in Authentication Module (high 8.8)
- [CVE-2026-33289](https://insights.sbomify.com/CVE-2026-33289/): SuiterCRM has LDAP Filter Injection in Authentication Module (high 8.8)
- [CVE-2026-29109](https://insights.sbomify.com/CVE-2026-29109/): SuiteCRM Authenticated Remote Code Execution via Unsafe Deserialization in SavedSearch Filter Processing (high 8.6)
- [CVE-2026-29096](https://insights.sbomify.com/CVE-2026-29096/): SuiteCRM vulnerable to Authenticated SQL Injection via unsanitized field_function in Report Fields (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-29103 and fix it if it is affected.

What it is: CVE-2026-29103 is a critical code injection vulnerability in SuiteCRM, published on 19 Mar 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-29103 in the wild and no public exploit code.

Affected product: SuiteCRM. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-29103/ (Markdown: https://insights.sbomify.com/CVE-2026-29103/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-29103
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-29103
- OSV: https://osv.dev/vulnerability/CVE-2026-29103

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-29103/
Summaries are generated and may contain mistakes; the official description above is the record.