Skip to content

SuiteCRM

Bug bounty on Sorona suitecrm.com

Accepting reports open-source
Top reward
$1,500
Top severity paid
Critical
Assets in scope
15
Public CVEs
50
Last change
No changes yet

At a glance

What to know before you start testing.

Pays from $1,500
for critical bugs.
Partial safe harbor
Some legal protection; read the terms.
Publish after a fix
Coordinate the timing with the company.

Rewards

What Sorona lists as the payout for each severity.

Severity Reward
Critical $1,500+
High $700+
Medium $300+
Low $100 $100 / 1 month Claude Max
Safe harbor
Partial Sorona will not pursue legal action against you for good-faith research submitted to us in line with this policy. We cannot speak for the upstream project, its vendor, or any third party, and we do not grant authorization on their behalf.

Summarised with AI from the program policy on Sorona, read 12 Nov 2026, and checked word for word against it. Read the original

Scope

15 assets you may test, 6 excluded.

Web 1

  • https://suitecrm.com

Products and areas 14

  • Authentication options in the tree, including LDAP and SAML, plus session handling and password reset
  • File attachments and the upload directory, both the write path and the retrieval check
  • Inbound and outbound email, including the inbound email monitor that parses messages from unauthenticated senders and the campaign and mass-mail surface
  • Record import and export, which parses user-supplied files and writes records from them
  • SecuritySuite security groups and roles, the record-level access control that decides who can see which customer
  • Studio and the module builder, where an administrator defines new modules and fields and the product writes PHP to disk
  • The customer-facing portal surface, where an external party signs in to see their own cases
  • The installer, the repair and rebuild tools and the upgrade wizard, all of which run with high privilege
  • The legacy core inherited from SugarCRM Community Edition: the bean layer, the module framework and the query construction underneath it
  • The policy asks for private reports through the GitHub advisory tab under a published community security policy, and it draws no component boundary. The whole SuiteCRM application is in scope on both supported lines
  • The reporting module and its filters, which build database queries from user-supplied criteria
  • The REST APIs, both the legacy v4.1 service and the V8 API with its OAuth2 token model
  • The SuiteCRM 8 front end and the API layer it talks to, which sits over that same legacy core
  • Workflow and the scheduler, which execute stored configuration as privileged background jobs
Out of scope (6)
  • Hosting and server configuration, including a deployment that serves the upload directory as executable
  • Releases outside the lines the project currently supports
  • Security group or role configuration an administrator chose deliberately
  • SugarCRM's commercial products, which are a different vendor's code
  • Third-party SuiteCRM extensions and modules distributed outside the core repository
  • Upstream PHP library issues, unless SuiteCRM's own use of the library is what makes the defect reachable

Rules

What the policy asks of you, and the bug types it won't reward, quoted from Sorona's policy. "We" in these lines means Sorona, not this site.

While testing

  • Submit through sorona.xyz. This project runs no bounty of its own; we validate, coordinate disclosure with the maintainers, and pay you directly.
  • Use the "Report a Vulnerability" tab on salesagility/SuiteCRM, the channel the SECURITY.md names
  • Read the fuller community security policy at docs.suitecrm.com before filing; it is the more detailed document and sets the expectations triage works to
  • Say which line you tested. SuiteCRM 7 and SuiteCRM 8 are different enough that a finding in one may not exist in the other, and 8 still carries the legacy core underneath
  • A defect inherited from SugarCRM Community Edition code still gets reported here. SugarCRM is a separate commercial vendor and is not the maintainer of this fork
  • Give the security group configuration your reproduction assumed. SecuritySuite record access is the product's main authorisation mechanism and a report without it cannot be reproduced
  • There is no reward tier and no payment to negotiate

Summarised with AI from the program policy on Sorona, read 12 Nov 2026, and checked word for word against it. Read the original

Changes

Tracked since 11 Nov 2026. Last checked 1 hour ago.

No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.

Public CVEs

Published vulnerabilities in this vendor's products, from the NVD.

Search NVD
CVESeverityPublished
CVE-2026-97377 High 8.8 5 Nov 2026
CVE-2026-69142 High 8.8 5 Nov 2026
CVE-2026-69144 Medium 6.5 5 Nov 2026
CVE-2026-69145 Medium 6.5 5 Nov 2026
CVE-2026-71548 High 8.8 5 Nov 2026
CVE-2026-71550 Critical 9.9 5 Nov 2026
CVE-2026-69134 High 8.8 5 Nov 2026
CVE-2026-69135 High 7.1 5 Nov 2026
CVE-2026-69136 High 7.1 5 Nov 2026
CVE-2026-69137 High 7.7 5 Nov 2026
CVE-2026-69140 High 8.3 5 Nov 2026
CVE-2026-69141 High 8.3 5 Nov 2026
CVE-2026-63214 High 8.8 5 Nov 2026
CVE-2026-63215 High 8.3 5 Nov 2026
CVE-2026-63217 Medium 6.5 5 Nov 2026
CVE-2026-63218 Medium 6.5 5 Nov 2026
CVE-2026-61650 High 8.1 5 Nov 2026
CVE-2026-61651 High 8.3 5 Nov 2026
CVE-2026-61653 High 8.3 5 Nov 2026
CVE-2026-63111 High 7.1 5 Nov 2026
CVE-2026-63213 High 7.2 5 Nov 2026
CVE-2026-61648 High 8.3 5 Nov 2026
CVE-2026-61649 High 7.7 5 Nov 2026
CVE-2026-100364 High 7.1 5 Nov 2026
CVE-2026-100365 High 8.8 5 Nov 2026
CVE-2026-100360 High 7.1 5 Nov 2026
CVE-2026-100361 High 7.1 5 Nov 2026
CVE-2026-100362 Medium 6.9 5 Nov 2026
CVE-2026-100363 High 8.8 5 Nov 2026
CVE-2026-100359 Medium 6.5 5 Nov 2026
CVE-2026-100358 Critical 9.4 5 Nov 2026
CVE-2026-33289 High 8.8 20 Mar 2026
CVE-2026-33288 High 8.8 20 Mar 2026
CVE-2026-32697 Medium 6.5 20 Mar 2026
CVE-2026-29108 Medium 6.5 20 Mar 2026
CVE-2026-29109 High 8.6 20 Mar 2026
CVE-2026-29189 High 8.1 20 Mar 2026
CVE-2026-29106 Medium 5.9 19 Mar 2026
CVE-2026-29107 Medium 5.0 19 Mar 2026
CVE-2026-29101 Medium 4.9 19 Mar 2026
CVE-2026-29102 High 7.2 19 Mar 2026
CVE-2026-29103 Critical 9.1 19 Mar 2026
CVE-2026-29104 Low 2.7 19 Mar 2026
CVE-2026-29105 Medium 5.4 19 Mar 2026
CVE-2026-29097 High 7.1 19 Mar 2026
CVE-2026-29098 Medium 4.9 19 Mar 2026
CVE-2026-29099 High 8.8 19 Mar 2026
CVE-2026-29100 High 7.1 19 Mar 2026
CVE-2026-29096 High 8.1 19 Mar 2026
CVE-2019-18785 High 7.5 20 Mar 2020

Original policy

Copied from sorona.xyz on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.

Skip to content What this pays This project runs no bounty of its own. sorona.xyz pays you directly on qualified, reproduced findings. Severity │ sorona.xyz pays Critical │ $1,500+ High │ $700+ Medium │ $300+ Low │ $100 / 1 month Claude Max Submit a vulnerability CVE history 24 Last 12 months 45 Lifetime Access control 35 % Injection 26 % XSS/CSRF 22 % RCE/file handling 17 % Latest advisories Loading the feed Overview SuiteCRM is the open-source successor to SugarCRM, deployed heavily across UK and European public-sector bodies and small businesses that keep citizen and customer records in it. The reference point for cost is who runs it: a council or a charity with a CRM full of named individuals and nobody watching for a compromise. Twenty-four of its forty-five published advisories arrived in the last twelve months, one of the three busiest unpaid pipelines in this category. SalesAgility takes reports through the GitHub advisory tab under a documented community policy and offers nothing in return, so sorona.xyz pays you directly on qualified, reproduced findings. In scope The policy asks for private reports through the GitHub advisory tab under a published community security policy, and it draws no component boundary. The whole SuiteCRM application is in scope on both supported lines The legacy core inherited from SugarCRM Community Edition: the bean layer, the module framework and the query construction underneath it The SuiteCRM 8 front end and the API layer it talks to, which sits over that same legacy core SecuritySuite security groups and roles, the record-level access control that decides who can see which customer The REST APIs, both the legacy v4.1 service and the V8 API with its OAuth2 token model Studio and the module builder, where an administrator defines new modules and fields and the product writes PHP to disk Workflow and the scheduler, which execute stored configuration as privileged background jobs The reporting module and its filters, which build database queries from user-supplied criteria Inbound and outbound email, including the inbound email monitor that parses messages from unauthenticated senders and the campaign and mass-mail surface Record import and export, which parses user-supplied files and writes records from them File attachments and the upload directory, both the write path and the retrieval check The installer, the repair and rebuild tools and the upgrade wizard, all of which run with high privilege Authentication options in the tree, including LDAP and SAML, plus session handling and password reset The customer-facing portal surface, where an external party signs in to see their own cases Out of scope SugarCRM's commercial products, which are a different vendor's code Third-party SuiteCRM extensions and modules distributed outside the core repository Security group or role configuration an administrator chose deliberately Upstream PHP library issues, unless SuiteCRM's own use of the library is what makes the defect reachable Hosting and server configuration, including a deployment that serves the upload directory as executable Releases outside the lines the project currently supports Most-valued findings SecuritySuite bypass, where a user reads or edits a record their security groups were supposed to exclude. On a public-sector CRM this is the difference between one caseworker's caseload and everybody's Studio and the module builder, where an administrative feature writes executable PHP to disk. Administrator in this product is often a business user rather than the server operator, so that gap is a real privilege boundary SQL injection through legacy query construction, report filters, list-view search or the v4.1 API. The inherited codebase assembles queries in many places and this is the densest class in its public history The upload directory and anything that lands a file with an executable extension where the web server will run it, plus path traversal in the attachment download route The legacy v4.1 REST service, which predates the current authorisation model and is still reachable on many deployments Authentication and session defects, including password reset, SAML assertion handling and session fixation Stored cross-site scripting in a contact, case or email record that later renders in an administrator's session, since administrator reaches Studio The inbound email monitor, one of the few paths where a complete stranger's content reaches server-side parsing with no account Scheduler and workflow jobs that act on low-privilege user input while running with elevated rights Unauthorised record disclosure through the portal, where an external account already holds valid credentials Program rules Submit through sorona.xyz. This project runs no bounty of its own; we validate, coordinate disclosure with the maintainers, and pay you directly. Use the "Report a Vulnerability" tab on salesagility/SuiteCRM, the channel the SECURITY.md names Read the fuller community security policy at docs.suitecrm.com before filing; it is the more detailed document and sets the expectations triage works to Say which line you tested. SuiteCRM 7 and SuiteCRM 8 are different enough that a finding in one may not exist in the other, and 8 still carries the legacy core underneath A defect inherited from SugarCRM Community Edition code still gets reported here. SugarCRM is a separate commercial vendor and is not the maintainer of this fork Give the security group configuration your reproduction assumed. SecuritySuite record access is the product's main authorisation mechanism and a report without it cannot be reproduced There is no reward tier and no payment to negotiate Disclosure Coordinated privately through the GitHub advisory tab and published as a GitHub Security Advisory alongside a patched release. At twenty-four advisories in a year the pipeline is visibly attended, and the public record shows SalesAgility batching fixes into releases rather than shipping them one at a time. No fixed embargo length is published. Time disclosure to the release that carries the fix, and account for public-sector operators who upgrade on a procurement cycle rather than a release cycle. Safe harbor Sorona will not pursue legal action against you for good-faith research submitted to us in line with this policy. We cannot speak for the upstream project, its vendor, or any third party, and we do not grant authorization on their behalf. You are responsible for understanding and following the laws that apply to you, wherever you are, and for staying within any scope the project has defined. Submit a vulnerability