CVE-2024-36415
Salesagility Suitecrm ≤ 7.14.4
Raw vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:HSummary
CVE-2024-36415 is a critical-severity PHP Remote File Inclusion (CWE-98) vulnerability in Salesagility Suitecrm. Its CVSS base score is 9.1 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 44% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
SuiteCRM, an open-source customer relationship management application, contains a flaw in its uploaded file verification logic that permits remote code execution. The issue affects all versions prior to 7.14.4 and 8.6.1 and is tracked under CWE-98 and CWE-434, reflecting improper control of filenames for include/require operations combined with unrestricted upload of dangerous file types.
An attacker with high privileges can exploit the vulnerability over the network with low attack complexity and no user interaction. Successful exploitation allows the attacker to upload a malicious file that bypasses verification checks, resulting in arbitrary code execution on the server with impacts to confidentiality, integrity Availability, and scope change.
The official GitHub Security Advisories for GHSA-c82f-58jv-jfrh state that the issue is resolved in SuiteCRM 7.14.4 and 8.6.1; administrators are advised to upgrade to these patched releases.
EPSS scores for the CVE rose from lower values to a peak of 0.0584 on 2025-12-11 before receding to the current 0.0400, indicating modest but detectable post-disclosure interest in exploitation.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-36072
Vulnerability Data
SuiteCRM is an open-source Customer Relationship Management (CRM) software application. Prior to versions 7.14.4 and 8.6.1, a vulnerability in uploaded file verification in products allows for remote code execution. Versions 7.14.4 and 8.6.1 contain a fix for this issue.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V5.1.1
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and static analysis can discover missing filename restrictions before deployment.
Validating all inputs before they reach include/require statements directly stops untrusted filenames from being used.
Malicious-code protection at entry points blocks dangerous file types from being accepted and executed.
Enforcing access authorizations on resources limits what an included file can reach even if a bad name is supplied.
Information-flow rules can block the loading of external or unauthorized files into the PHP process.
Least functionality restricts the file types and automatic processing capabilities the system will accept.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Restricting execution of unauthorized software directly blocks dangerous uploaded files from running.
Secure SDLC practices such as input validation and allow-listing of include paths directly prevent the weakness.
Hardened runtime configuration (e.g., allow_url_include=off) directly blocks RFI even if code is flawed.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect RFI but does not prevent the weakness by itself.
Secure development lifecycle mandates input validation and safe include/require patterns that directly prevent remote file inclusion.
Application security requirements explicitly call for controls against injection and unsafe file operations.
Secure architecture principles reduce attack surface but do not specifically address dynamic file inclusion.
Secure coding standards directly require whitelisting and sanitization of filenames used in include/require statements.
Mandated testing for malicious content and known vulnerabilities reduces the likelihood that an outsourced component will contain or accept dangerous file types that could later be uploaded or executed.