Skip to content
bugbounty.fyi
Get paid to secure open source 475 paid open-source programs on Sorona, up to $1M Perk Low bugs: $100 or 1 mo Claude Max

Also on Patchstack. All 476 paid open-source programs

Try

Highest paying Newly launched Paid without KYC Full safe harbor
All results

About this site

amoCRM

By Kommo Vulnerability disclosure program on Self-hosted kommo.com

Accepting reports Full safe harbor
Go to program Website
Top reward
No cash rewards
Top severity paid
Not published
Assets in scope
4
Public CVEs
0
Last change
No changes yet

At a glance

What to know before you start testing.

No cash rewards
A disclosure program: you report for credit, not money.
Report by email
[email protected]
Full safe harbor
Good-faith research is authorised; no legal action.
Publish after a fix
Coordinate the timing with the company.

Rewards

What the company's own policy page says it pays.

This program does not pay cash rewards.

Pays cash
No We are not obliged to provide remuneration, fee or rewards for any vulnerability disclosure – such action remains in our full discretion.
Safe harbor
Full Authorized in accordance with the Computer Fraud and Abuse Act (CFAA) (and/or similar state laws), and we will not initiate or support legal action against you for accidental, good faith violations of this Disclosure Program when conducting genuine vulnerability research.

Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original

Scope

4 assets you may test, 21 excluded.

Domains 1

  • kommo.com

Web 1

  • https://www.kommo.com

Wildcard domains 1

  • any of third level subdomain kommo.com

Products and areas 1

  • Anything with significant impact across our entire security posture or infrastructure
Out of scope (21)
  • Attacks designed or likely to degrade, deny, or adversely impact services or user experience (e.g., Denial of Service, Distributed Denial of Service, Brute Force, Password Spraying, Spam...).
  • Attacks designed or likely to destroy, corrupt, make unreadable (or attempts therein) data or information that does not belong to you.
  • Attacks designed or likely to validate stolen credentials, credential reuse, account takeover (ATO), hijacking, or other credential-based techniques.
  • Attacks performed on any systems not explicitly mentioned as authorized and in-scope.
  • Attacks related to email servers, email protocols, email security (e.g., SPF, DMARC, DKIM), or email spam.
  • Clickjacking or self-XSS reports.
  • Domain-based phishing, typosquatting, punycodes, bitflips, or other techniques.
  • Email security best practices or controls (e.g. SPF, DKIM, DMARC).
  • Intentionally accessing data or information that does not belong to you beyond the minimum viable access necessary to demonstrate the vulnerability.
  • Missing cookie flags on non-sensitive cookies.
  • Missing HTTP headers (e.g. lack of HSTS).
  • Performing physical, social engineering, or electronic attacks against our personnel, offices, wireless networks, or property.
  • Reports of how you can learn whether a given client can authenticate to a Kommo product or service.
  • Reports of insecure SSL/TLS ciphers (unless accompanied with working proof of concept).
  • Reports of mappings between code names and client names.
  • Reports of missing “best practices” or other guidelines which do not indicate a security issue.
  • Reports of publicly resolvable or accessible DNS records for internal hosts or infrastructure.
  • Reports of simple IP or port scanning.
  • Security issues or vulnerabilities created or introduced by the reporter (e.g., modifying a library we rely on to include a vulnerability for the sole purpose of receiving a reward).
  • Software or infrastructure bannering, fingerprinting, or reconnaissance with no proven vulnerability.
  • Violating any laws or breaching any agreements (or any reports of the same).

Rules

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

While testing

  • Do not cause any harm, hinder application fluency or act against our Terms of Use Agreement
  • Do not intentionally access non-public Kommo data anymore than is necessary to demonstrate the vulnerability.
  • If a vulnerability provides unintended access to data, please cease testing, purge local information, and submit a report immediately.
  • Keep the details of any discovered vulnerabilities confidential, according to this Disclosure Program.
  • Use only the official channels designated (see “Reporting”) to discuss vulnerability information with us
  • We accept only manual or semi-manual tests.

Not accepted

  • All findings coming from automated tools or scripts will be considered as out of scope.
  • all issues without clearly identified security impact, missing security headers, or descriptive error messages will be considered out of scope
  • Denial of Service, Distributed Denial of Service, Brute Force, Password Spraying, Spam
  • Missing cookie flags on non-sensitive cookies.
  • Reports of insecure SSL/TLS ciphers (unless accompanied with working proof of concept).
  • Reports of simple IP or port scanning.
  • Missing HTTP headers (e.g. lack of HSTS).
  • Clickjacking or self-XSS reports.
  • Domain-based phishing, typosquatting, punycodes, bitflips, or other techniques.
  • Reports of missing “best practices” or other guidelines which do not indicate a security issue.

Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original

Changes

Tracked since 11 Nov 2026. Last checked 5 hours 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

No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.