- Top reward
- Not published
- Top severity paid
- Not published
- Assets in scope
- 1
- Public CVEs
- 0
- Last change
- No changes yet
At a glance
What to know before you start testing.
- Pays cash
- Amounts are not published; ask before you invest time.
- Report by email
- [email protected]
- Full safe harbor
- Good-faith research is authorised; no legal action.
- Payment
- Proof of identity needed to get paid.
- No public write-ups
- Keep findings private.
Rewards
What the company's own policy page says it pays.
The policy page has no reward table. Here is what it says, in its own words.
- Pays cash
-
Yes
All confirmed vulnerabilities will be considered, assessed and awarded a bounty based on severity as determined by our in-house team.
- Safe harbor
-
Full
Any activities conducted in a manner consistent with this policy will be considered authorised conduct and we will not initiate legal action against you.
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
1 asset you may test, 6 excluded.
Domains 1
- global.com
Out of scope (6)
- captivate.fm
- globalacademy.com
- mmdmedia.nl
- whistleblowing.global.com
- any domains that relate to Shopify
- Global’s Honeypots and deception tools
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Global's policy. "We" in these lines means the program, not this site.
While testing
-
Do not break the law;
-
Do not use social engineering techniques, phishing, or physical attacks against our customers, infrastructure or staff;
-
Do not perform any attack that could harm the reliability or integrity of our systems, services or data. DoS and/or spam attacks are not allowed;
-
Do not put any Global data or customer data at risk;
-
Do not make the bug public; and
-
Minimise requests and content submissions
-
Avoid impacting real users, customers, or production data
-
Stop testing immediately if disruption occurs
-
Upon Global’s request, you will agree and sign: (i) a Non-Disclosure Agreement; and (ii) a Letter of Undertakings
Not accepted
-
DoS or DDoS.
-
Destructive or performance-impacting attacks or testing.
-
Social engineering or Phishing.
-
Submissions relating to clickjacking.
-
Submissions relating to tabnabbing.
-
Submissions of TLS configuration weaknesses (e.g. “weak” ciphersuite support, TLS1.0, TLS1.1 support, sweet32 etc.) or Certificate issues.
-
User account Authentication Best Practices (e.g. Lack of Password Confirmation, Failure to Invalidate Session, or Concurrent Logins)
-
Vulnerabilities related to SRI.
-
Autocomplete attribute on web forms.
-
CSRF vulnerabilities.
-
Simple rate-limiting issues without a security impact.
-
Submissions entirely comprising output from commonly available automated scanners.
-
Vulnerabilities that require the target device to be in an unlocked or unattended state.
-
Parameter Pollution without proof of bypassing authentication mechanisms, manipulating business logic, or remote code execution.
-
Host header injection without proof of user data extraction.
-
SQLi without proof of user data extraction.
-
Software version disclosure and verbose error pages without proof of exploitability.
-
Open ports without an accompanying proof-of-concept demonstrating exploitability.
-
Use of outdated software/library versions without an accompanying proof-of-concept demonstrating exploitability.
-
Disclosure of known public files or directories.
-
Zero-day or recent vulnerabilities disclosed within the past 30 days where a patch is unavailable.
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.
No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.