CVE-2026-29105
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, SuiteCRM contains an unauthenticated open redirect vulnerability in the WebToLead capture functionality. A user-supplied POST parameter is used as a redirect destination without validation, allowing attackers to redirect victims to arbitrary external websites. This vulnerability allows attackers to abuse the trusted SuiteCRM domain for phishing and social engineering attacks by redirecting users to malicious external websites. 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 contains an unauthenticated open redirect vulnerability in the WebToLead capture functionality. Attackers can supply a malicious POST parameter that gets used as a redirect destination without validation, allowing redirection to arbitrary external websites while abusing the trusted SuiteCRM domain.
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.
-
Determine installed SuiteCRM versionLocate the version number in the SuiteCRM admin panel (About section) or check the version.php /suite_version.php file in the installation root directoryAffected if The version is less than 7.15.1 OR greater than or equal to 8.0.0 but less than 8.9.3
-
Confirm WebToLead module is accessibleVerify that the WebToLead capture form endpoint is reachable - typically at /index.php?module=WebToLeadCapture or similar path under the SuiteCRM rootAffected if WebToLead functionality is enabled and accessible without authentication
-
Identify the redirect parameter handlingExamine the WebToLead form handling code - check if POST parameters controlling redirect behavior are validated before use in header() or similar redirect functionsAffected if The code uses unchecked POST parameters for redirect destinations without validating they point to internal URLs
You are affected if your SuiteCRM version falls within the vulnerable ranges (< 7.15.1 or >= 8.0.0 to < 8.9.3) AND the WebToLead module is enabled and accessible without validation on redirect parameters.
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 versions 7.15.1 or 8.9.3 which contain the patch. Until then, implement temporary validation on redirect parameters in the WebToLead module.
SuiteCRM 7.15.1 (for 7.x versions) or SuiteCRM 8.9.3 (for 8.x versions)
- 1. Identify your current SuiteCRM version by accessing the admin panel or checking the version.php file in the installation directory
- 2. For SuiteCRM 7.x installations (version < 7.15.1): Upgrade to version 7.15.1 or later
- 3. For SuiteCRM 8.x installations (version >= 8.0.0 and < 8.9.3): Upgrade to version 8.9.3 or later
- 4. Download the appropriate upgrade package from the official SuiteCRM website (suitecrm.com) or GitHub repository
- 5. Follow the standard SuiteCRM upgrade procedure: backup your database and files, disable maintenance mode, extract the upgrade package, run the upgrade wizard
- 6. After completing the upgrade, clear the cache by deleting contents of the cache/ folder
- 7. Verify the WebToLead functionality works correctly with the new version
- 8. Test that the open redirect vulnerability is remediated by confirming that arbitrary external URLs can no longer be used as redirect destinations in the WebToLead form
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.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 $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-29105 — 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-29105 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