CVE-2026-29106
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. 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.
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 prior to 7.15.1 and 8.9.3 contain a reflected cross-site scripting (XSS) vulnerability where the return_id request parameter is directly copied into an HTML event handler attribute without proper sanitization, allowing attacker-controlled JavaScript 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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.
-
Check installed SuiteCRM versionLocate the version file in your SuiteCRM installation. For 7.x, check include/SuiteCRM/SuiteCRM.php or the About page. For 8.x, check the version file in the vendor directory or the About page in the UI.Affected if The installed version is below 7.15.1 for the 7.x branch, or below 8.9.3 for the 8.x branch.
-
Identify return_id parameter handlingSearch your codebase for usage of the 'return_id' request parameter, particularly in files that handle form submissions or redirects. Use grep to search for 'return_id' in PHP files.Affected if The application processes the return_id parameter from HTTP requests without sanitization.
-
Verify output encoding for return_idExamine the code paths where return_id is used in HTML context. Check if htmlspecialchars or equivalent encoding is applied before the value is placed into HTML event handler attributes.Affected if The return_id value is inserted into HTML event handler attributes without proper output encoding.
-
Check for CSP header deploymentReview your web server configuration (Apache/Nginx) and SuiteCRM config for Content-Security-Policy headers that could mitigate XSS.Affected if No CSP header is configured to mitigate XSS, leaving the reflected XSS fully exploitable.
You are affected if your SuiteCRM version is below 7.15.1 (7.x) or below 8.9.3 (8.x) and the application processes the return_id parameter without sanitization.
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 or later to patch the vulnerability, and implement a Content Security Policy header as an additional defensive measure.
7.15.1 for 7.x line; 8.9.3 for 8.x line
- 1. Identify which major version line (7.x or 8.x) your SuiteCRM instance is running
- 2. For 7.x versions: Upgrade to SuiteCRM 7.15.1 or later
- 3. For 8.x versions: Upgrade to SuiteCRM 8.9.3 or later
- 4. After upgrading, verify the return_id parameter is properly sanitized and no longer vulnerable to XSS
- 5. As an additional defense-in-depth measure, implement a Content Security Policy (CSP) header to completely mitigate any remaining XSS vectors
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-29106 — 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-29106 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