What is the CVSS score of CVE-2026-29106?

CVE-2026-29106 has a CVSS 3.1 base score of 5.9 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:L. EPSS exploitation probability: 0.0%.

Which versions of Suitecrm are affected by CVE-2026-29106?

Organizations using SuiteCRM should be aware of moderate risk from CVE-2026-29106, a cross-site scripting vulnerability rated CVSS 5.9.

How to fix or mitigate CVE-2026-29106?

Within 30 days: Identify affected systems and apply vendor patches as part of regular patch cycle. Verify Content-Security-Policy and output encoding.

Suitecrm CVE-2026-29106

MEDIUM

Cross-site Scripting (XSS) (CWE-79)

2026-03-19 security-advisories@github.com

XSS Suitecrm

5.9

CVSS 3.1 · GitHub Advisory

Severity by source

GitHub Advisory PRIMARY

5.9 MEDIUM

AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:L

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:L

Attack Vector

Network

Attack Complexity

Low

Privileges Required

High

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

Low

Lifecycle Timeline

Analysis Generated

Mar 19, 2026 - 23:30 vuln.today

CVE Published

Mar 19, 2026 - 23:16 nvd

MEDIUM 5.9

DescriptionGitHub Advisory

SuiteCRM is an open-source, enterprise-ready Customer Relationship Management (CRM) software application. Prior to versions 7.15.1 and 8.9.3, the value of the return_id request parameter is copied into the value of an HTML tag attribute which is an event handler and is encapsulated in double quotation marks. Versions 7.15.1 and 8.9.3 patch the issue. Users should also use a Content Security Policy (CSP) header to completely mitigate XSS.

AnalysisAI

SuiteCRM versions prior to 7.15.1 and 8.9.3 contain a stored cross-site scripting (XSS) vulnerability in the return_id request parameter, which is insufficiently sanitized before being reflected into HTML event handler attributes. An authenticated attacker with high privileges can craft malicious payloads that execute arbitrary JavaScript in the context of other users' browsers, potentially leading to session hijacking, credential theft, or unauthorized actions performed on behalf of victims. While this vulnerability requires authenticated access and user interaction to trigger, it affects a widely-deployed open-source CRM platform used by many enterprises.

Technical ContextAI

The vulnerability is a classic reflected XSS flaw (CWE-79: Improper Neutralization of Input During Web Page Generation) in a PHP-based web application. SuiteCRM fails to properly encode or sanitize the return_id parameter before inserting it into an HTML event handler attribute (such as onclick, onload, or onerror) enclosed in double quotes. This allows attackers to break out of the attribute context by closing the quote and injecting arbitrary event handler code or script content. The root cause is insufficient input validation and output encoding at the point where user-controlled data is reflected into the DOM. As a CRM system handling sensitive customer data, SuiteCRM's role in enterprise environments amplifies the impact of this flaw, though it is mitigated somewhat by the requirement for authenticated access (PR:H in the CVSS vector).

RemediationAI

Upgrade SuiteCRM to version 7.15.1 or later on the 7.x branch, or to version 8.9.3 or later on the 8.x branch (see vendor advisory at https://github.com/SuiteCRM/SuiteCRM/security/advisories/GHSA-7qrj-5hj6-7c2m and release notes at https://docs.suitecrm.com/admin/releases/7.15.x). If immediate patching is not possible, implement a Content Security Policy (CSP) header on the SuiteCRM web server to prevent inline script execution; this will mitigate XSS attacks even if malicious payloads are injected. Additionally, restrict administrative and high-privilege account access to trusted networks or IP ranges, conduct security awareness training for administrators regarding phishing attacks that could compromise high-privilege accounts, and monitor access logs for suspicious activity from authenticated accounts. Apply web application firewall (WAF) rules to detect and block common XSS payloads in the return_id parameter as a temporary compensating control.