CVE-2026-29104

SuiteCRM is an open-source, enterprise-ready Customer Relationship Management (CRM) software application.

Verified by Precogs Threat Research
Last Updated: Mar 20, 2026
Base Score
2.7LOW

Executive Summary

CVE-2026-29104 is a low severity vulnerability affecting appsec, ai-code. It is classified as Unrestricted Upload. Ensure your systems and dependencies are patched immediately to mitigate exposure risks.

Precogs AI Insight

"Architecturally, this flaw occurs due to within SuiteCRM, allowing insufficient sanitization protocols during data parsing. By manipulating this weakness, a threat actor can inject malicious logic that alters the execution flow of the application engine. The Precogs AI's Code Property Graph analysis traces untrusted input to intercept unsafe execution patterns."

Exploit Probability (EPSS)
Low (0.0%)
Public POC
Undisclosed
Exploit Probability
Low (<10%)
Public POC
Available
Affected Assets
appsecai codeCWE-434

What is this vulnerability?

CVE-2026-29104 is categorized as a critical Code Injection / RCE flaw. Based on our vulnerability intelligence, this issue occurs when the application fails to securely handle untrusted data boundaries.

SuiteCRM is an open-source, enterprise-ready Customer Relationship Management (CRM) software application. Prior to versions 7.15.1 and 8.9.3, SuiteCRM cont...

This architectural defect enables adversaries to bypass intended security controls, directly manipulating the application's execution state or data layer. Immediate strategic intervention is required.

Risk Assessment

MetricValue
CVSS Base Score2.7 (LOW)
Vector StringCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N
PublishedMarch 19, 2026
Last ModifiedMarch 20, 2026
Related CWEsCWE-434

Impact on Systems

Remote Code Execution: Attackers achieve arbitrary command execution within the context of the application server.

Privilege Escalation: Initial code execution can be exploited to pivot and elevate privileges across the network.

Persistent Backdoors: Attackers can bind reverse shells, modify source files, or inject persistent access mechanisms.

How to fix this issue?

Implement the following strategic mitigations immediately to eliminate the attack surface.

1. Remove Dynamic Evaluation Completely eliminate the use of dynamic evaluation functions (eval(), exec(), system()) on untrusted input.

2. Sandboxing If dynamic execution is an absolute business requirement, isolate the execution environment in tightly constrained, non-networked sandboxes (e.g., restricted WebAssembly or isolated containers).

3. Network Segmentation Restrict outbound traffic from the application server (egress filtering) to prevent reverse shell connections.

Vulnerability Signature

// Vulnerable Node.js Execution
const exec = require('child_process').exec;
const user_domain = req.query.domain;
// VULNERABLE: Injecting user input directly into system shell commands
exec('ping -c 4 ' + user_domain, (error, stdout, stderr) =\> \{
    res.send(stdout);
\});

// EXPLOIT PAYLOAD: precogs.ai ; cat /etc/passwd

References and Sources

Vulnerability Code Signature

Attack Data Flow

StageDetail
SourceUser-uploaded file
VectorFile is saved to a web-accessible directory without validation
SinkFile system write operation
ImpactRemote Code Execution (RCE), full system compromise

Vulnerable Code Pattern

// ❌ VULNERABLE: Unrestricted Upload
$target_dir = "uploads/";
$target_file = $target_dir . basename($_FILES["fileToUpload"]["name"]);
// Taint sink: saving file without extension/type validation
move_uploaded_file($_FILES["fileToUpload"]["tmp_name"], $target_file);

Secure Code Pattern

// ✅ SECURE: Validated Upload
$target_dir = "uploads/";
$filename = basename($_FILES["fileToUpload"]["name"]);
$filetype = strtolower(pathinfo($filename, PATHINFO_EXTENSION));

// Sanitized validation: strict allowlist
$allowed_types = array("jpg", "png", "gif");
if (in_array($filetype, $allowed_types)) {
    // Generate safe unique filename
    $safe_filename = uniqid() . "." . $filetype;
    move_uploaded_file($_FILES["fileToUpload"]["tmp_name"], $target_dir . $safe_filename);
}

How Precogs Detects This

Precogs AI Analysis Engine utilizes semantic taint tracking to detect insecure file upload routines and missing extension validation.\n

Related Vulnerabilitiesvia CWE-434

Is your system affected?

Precogs AI detects CVE-2026-29104 in compiled binaries, LLMs, and application layers — even without source code access.