CVE-2026-29103
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSuiteCRM 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceSuiteCRM versions 7.15.0 and 8.9.2 contain a patch bypass of CVE-2024-49774 where ModuleScanner.php incorrectly resets its internal $checkFunction flag when encountering single-character PHP tokens (=, ., or ;). This allows authenticated administrators to hide dangerous function calls like system() or exec() using variable assignments or string concatenation, bypassing MLP security controls and achieving arbitrary code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 7.15.1>= 8.0.0, < 8.9.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed SuiteCRM versionAccess the SuiteCRM admin panel and navigate to Admin > System Settings, or check the version.php file in the SuiteCRM root directory. Record the exact version number.Affected if The installed version is 7.15.0 OR 8.9.2, OR falls in the range < 7.15.1 (for 7.x versions), OR >= 8.0.0 and < 8.9.3 (for 8.x versions).
-
Locate and inspect ModuleScanner.phpFind the ModuleScanner.php file within the SuiteCRM installation, typically in the src/Security or similar directory under the SuiteCRM 8 codebase. Open the file and locate the section handling the $checkFunction flag and single-character PHP token processing.Affected if The file contains logic that processes single-character tokens (=, ., or ;) and appears to reset or modify the $checkFunction flag based on these tokens, indicating the vulnerable code pattern exists.
-
Verify Module Loader Package (MLP) functionality is accessibleLog in as an administrator and navigate to the Module Loader interface in the admin panel. Confirm whether MLP upload and installation features are available and enabled for administrator accounts.Affected if The MLP functionality is enabled and accessible to administrator accounts, allowing package uploads that would trigger the ModuleScanner.php validation logic.
-
Review administrator accounts for suspicious activityAudit the SuiteCRM admin user list in Admin > User Management. Check for newly created admin accounts, unauthorized password changes, or admin sessions from unfamiliar IP addresses. Review the audit log for administrative actions taken around the time of potential exploitation.Affected if Unexpected admin accounts exist, admin credentials have been changed without authorization, or suspicious administrative actions are logged indicating potential exploitation of this vulnerability.
A user is affected if their SuiteCRM installation runs version 7.15.0, 8.9.2, or any version in the ranges < 7.15.1 or >= 8.0.0 to < 8.9.3, and the MLP functionality is accessible to administrators who could potentially exploit the ModuleScanner.php bypass.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped7.15.18.9.3
Upgrade to SuiteCRM version 7.15.1 or 8.9.3 immediately. Review admin accounts for compromise and monitor for suspicious administrative activity.
SuiteCRM 7.15.1 (for 7.x branch) or SuiteCRM 8.9.3 (for 8.x branch)
- 1. Perform a complete backup of the SuiteCRM database and all application files
- 2. Download the appropriate fixed version (7.15.1 for 7.x branch or 8.9.3 for 8.x branch) from the official SuiteCRM repository
- 3. Replace all application files with the new version files, preserving custom modules and themes in the appropriate directories
- 4. If using a non-standard theme, ensure compatibility with the new version
- 5. Clear all cache directories (cache/, data/, upload/) to remove any cached vulnerable code
- 6. Run the database repair and rebuild functions via Admin > Repair > Quick Repair and Rebuild
- 7. Clear the browser cache and test that the application functions correctly
- 8. Verify the fix by confirming that the ModuleScanner.php has the corrected token parsing logic that no longer resets $checkFunction on single-character tokens
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-29103 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-29103 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data