- Top reward
- €2,625
- Top severity paid
- Critical
- Assets in scope
- 20
- Public CVEs
- 0
- Last change
At a glance
What to know before you start testing.
- Pays up to €2,625
- for critical bugs, from €5.
- Report on Intigriti
- Submit through the program page.
- Full safe harbor
- Good-faith research is authorised; no legal action.
- No public write-ups
- Keep findings private.
Rewards
What Intigriti lists as the payout for each severity.
| Severity | Relative size | Reward |
|---|---|---|
| Critical |
|
€2,625 from €400 |
| High |
|
€700 from €100 |
| Medium |
|
€325 from €25 |
| Low |
|
€75 from €5 |
Scope
20 assets you may test.
Web 9
- api.cm.com
- api.cmtelecom.com
- appmiral.com
- building-blocks.com
- cm.com/app/messagingtrial
- cmcom.atlassian.net
- cm.com/[locale]/register
- login.cm.com
- www.cm.com
Wildcard domains 6
- *.appmiral.com
- *.cm.com
- cm.com/[locale]/app/*
- *.cmtelecom.com
- demo.globalticket.com/*
- *.ticketing.cm.com
Android apps 2
- com.cm.cashregister
- com.ticketflow.ticketscanner
iOS apps 2
- 1199521324
- 1579530451
Products and areas 1
- https://github.com/cmdotcom
Rules
What the policy asks of you, and the bug types it won't reward, quoted from CM.com (via Intigriti)'s policy. "We" in these lines means the program, not this site.
While testing
-
Respect the scope of the program
-
Not discuss or disclose vulnerability information without prior written consent (including PoC’s on YouTube and Vimeo)
-
Please do *not* use automatic scanners -be creative and do it yourself! We cannot accept any submissions found by using automatic scanners.
-
Please use your @intigriti.me accounts, otherwise it is highly likely you **will be blocked.**
Not accepted
-
API key disclosure without proven business impact
-
Wordpress usernames disclosure
-
Pre-Auth Account takeover/OAuth squatting
-
Self-XSS that cannot be used to exploit other users
-
Verbose messages/files/directory listings without disclosing any sensitive information
-
CORS misconfiguration on non-sensitive endpoints
-
Missing cookie flags
-
Missing security headers
-
Cross-site Request Forgery with no or low impact
-
Presence of autocomplete attribute on web forms
-
Reverse tabnabbing
-
Bypassing rate-limits or the non-existence of rate-limits.
-
Best practices violations (password complexity, expiration, re-use, etc.)
-
Clickjacking without proven impact/unrealistic user interaction
-
CSV Injection
-
Sessions not being invalidated (logout, enabling 2FA, etc.)
-
Tokens leaked to third parties
-
Anything related to email spoofing, SPF, DMARC or DKIM
-
Content injection without being able to modify the HTML
-
Username/email enumeration
-
Email bombing
-
HTTP Request smuggling without any proven impact
-
Homograph attacks
-
XMLRPC enabled
-
Banner grabbing/Version disclosure
Summarised with AI from the program policy on Intigriti, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 41 minutes ago.
No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.
Before we tracked it
Scope and reward changes recorded before this page started tracking it.
-
Status
Program status changed
-
Status
Program status changed
-
Status
Program status changed
-
Status
Program status changed
-
Scope removed
appmiral.com
-
Scope removed
*.cm.com
-
Scope removed
api.cm.com
-
Scope removed
*.ticketing.cm.com
-
Scope removed
cmcom.atlassian.net
-
Scope removed
1199521324
-
Scope removed
*.cmtelecom.com
-
Scope removed
www.cm.com
-
Scope removed
cm.com/app/messagingtrial/
-
Scope removed
cm.com/[locale]/register
-
Scope removed
building-blocks.com
-
Scope removed
com.cm.cashregister
-
Scope removed
com.ticketflow.ticketscanner
-
Scope removed
https://github.com/cmdotcom
-
Scope removed
login.cm.com
-
Scope removed
*.appmiral.com
-
Scope removed
1579530451
-
Scope removed
api.cmtelecom.com
-
Scope removed
demo.globalticket.com/*
-
Scope removed
cm.com/[locale]/app/*
Public CVEs
Published vulnerabilities in this vendor's products, from the NVD.
No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.
Original policy
Copied from www.intigriti.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.
Description
CM.com is a listed company that provides Conversational Commerce services from its hybrid cloud platform with in-house developed software.
CM.com’s customer base is spread over 118 countries, generating messages to more than 220 destinations.
Customers include Tier 1 enterprises, government agencies, as well as small and medium sized enterprises.
We offer API's for most of our products. You may find the documentation here: https://developers.cm.com
Rules of engagement
By participating in this program, you agree to:
- Respect the Community Code of Conduct
- Respect the Terms and Conditions
- Respect the scope of the program
- Not discuss or disclose vulnerability information without prior written consent (including PoC’s on YouTube and Vimeo)
- Please do not use automatic scanners -be creative and do it yourself! We cannot accept any submissions found by using automatic scanners. Scanners also won't improve your skills, and can cause a high server load (we'd like to put our time in thanking researchers rather than blocking their IP's 😉)
Usage of AI:
We welcome the use of AI to find and report vulnerabilities! We do ask that you do not submit any sensitive personal data to the AI vendor of your choosing whenever possible. For example, if you find a bug that exposes some personal data which you want to include as POC in your report, and you task your AI to make a report from your notes, please use placeholders and fill in the POC data when submitting the report to Intigriti.
In scope
Important! Please use your @intigriti.me accounts, otherwise it is highly likely you will be blocked.
We are specifically looking for:
- leaking of personal data
- SQLi
- RCE
Please do not use the following methods:
- Bruteforce -> Password / Username bruteforce
- Directory / file / content enumeration: see rate limit guidelines
- Testing on live customer environments like apps, ticketing shops etc. in ways that bother our customers e.g. creating accounts, posting payloads, signing up for free events, send payloads in support fields etc.
Our API's You can use the platform or API's (docs) to use products.
New Application: Ticketing How does this work? Login to your account and go to https://www.cm.com/en-gb/app/ticketing/ From here you can create tickets and much more! Make sure to take a look at the user-side as well (https://reserve.cmtickets.com/{GUID-OF-TICKET})
Out of scope
Out of scope Domains
- All domains that fall outside the scope that we listed.
Application
- API key disclosure without proven business impact
- Wordpress usernames disclosure
- Pre-Auth Account takeover/OAuth squatting
- Self-XSS that cannot be used to exploit other users
- Verbose messages/files/directory listings without disclosing any sensitive information
- CORS misconfiguration on non-sensitive endpoints
- Missing cookie flags
- Missing security headers
- Cross-site Request Forgery with no or low impact
- Presence of autocomplete attribute on web forms
- Reverse tabnabbing
- Bypassing rate-limits or the non-existence of rate-limits.
- Best practices violations (password complexity, expiration, re-use, etc.)
- Clickjacking without proven impact/unrealistic user interaction
- CSV Injection
- Sessions not being invalidated (logout, enabling 2FA, etc.)
- Tokens leaked to third parties
- Anything related to email spoofing, SPF, DMARC or DKIM
- Content injection without being able to modify the HTML
- Username/email enumeration
- Email bombing
- HTTP Request smuggling without any proven impact
- Homograph attacks
- XMLRPC enabled
- Banner grabbing/Version disclosure
- Not stripping metadata of files
- Same-site scripting
- Subdomain takeover without taking over the subdomain
- Arbitrary file upload without proof of the existence of the uploaded file
- Blind SSRF without proven business impact (pingbacks are not sufficient)
- Disclosed/misconfigured Google Maps API keys
- Host header injection without proven business impact
General
- In case that a reported vulnerability was already known to the company from their own tests, it will be flagged as a duplicate
- Theoretical security issues with no realistic exploit scenario(s) or attack surfaces, or issues that would require complex end user interactions to be exploited
- Spam, social engineering and physical intrusion
- DoS/DDoS attacks or brute force attacks
- Vulnerabilities that only work on software that no longer receive security updates
- Attacks requiring physical access to a victim's computer/device, man in the middle or compromised user accounts
- Recently discovered zero-day vulnerabilities found in in-scope assets within 14 days after the public release of a patch or mitigation may be reported, but are usually not eligible for a bounty
- Reports that state that software is out of date/vulnerable without a proof-of-concept
- Leaked credential lists, databases, monitoring services and marketplaces may be reported, but are not eligible for a bounty following Intigriti's recommendation:
- In general, we do not recommend to issue bounties to reporters who responsible disclose leaked secrets originating from credential marketplaces. While reporters may be act in good-faith and trying to help, they may be indirectly funding the activities of cyber criminals by purchasing this data. Programs that issue bounties for these credentials may further incentivise that and encourage cybercriminals to further conduct attacks against their assets. https://kb.intigriti.com/en/articles/8128339-reporting-leaked-secrets-credentials
Severity
This programs follows Intigriti's triage standards.
FAQ
Where can we get credentials for the app?
You can self-register on the application but please don’t forget to use your @intigriti.me address.
I do not see the Ticketing application in the 
?
That's possible, you can find the appliction by going to https://www.cm.com/en-gb/app/ticketing/
How do I access the Mobile Marketing Cloud?
As of now we don’t proactively provide access to the MMC. You are allowed to request access, but the Security team has no influence in accepting your request.
Where do I find API documentation?
Take a look at our !