Skip to content

TMG Security

Vulnerability disclosure program on Self-hosted tmgsec.com

Accepting reports
Top reward
No cash rewards
Top severity paid
Not published
Assets in scope
2
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]
No public write-ups
Keep findings private.

Rewards

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

This program does not pay cash rewards.

Pays cash
No We are not part of a cash/bug bounty program but are happy to issue a certificate of recognition to individuals who report security issues responsibly and help us make TMG Security systems more secure.
Hall of fame
Yes We sincerely appreciate the efforts of each individual listed in our wall of fame and we thank them for their technical skills, security knowledge, and constructive engagement with TMG Security.

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

Scope

2 assets you may test, 1 excluded.

Web 2

  • https://courses.tmgsec.com
  • https://tmgsec.com
Out of scope (1)
  • Any subdomain or asset owned by TMG Security other than the two mentioned above

Rules

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

While testing

  • Do not take advantage of the vulnerability or problem you have discovered, for example by downloading more data than necessary to demonstrate the vulnerability or deleting or modifying other people’s data.
  • Do not reveal the problem to others until it has been resolved.
  • Do not use attacks on physical security, social engineering, distributed denial of service, spam, etc.
  • Don’t exploit your finding.
  • Share the information with just us, not other parties.
  • Give us time to analyze the situation and fix the bug.

Not accepted

  • HTTP 404 codes/pages or other HTTP non-200 codes/pages and Content Spoofing/Text Injection on these pages.
  • Automation Scanner Vulnerabilities / CVE’s
  • Fingerprint and other ways to versions are disclosed on common/public services.
  • Disclosure of known public files or directories or non-sensitive information, (e.g. directories set up for downloads).
  • Clickjacking and issues only exploitable through clickjacking.
  • Login / Logout CSRF
  • Open Redirect – Unless it’s escalated to another severe issue.
  • Lack of Secure / HTTP Only flags on non-sensitive Cookies.
  • OPTIONS HTTP method enabled.
  • Weak Password Vulnerability
  • WordPress Vulnerabilities
  • Anything related to HTTP security headers, e.g.:
  • Strict-Transport-Security.
  • X-Frame-Options.
  • X-XSS-Protection.
  • X-Content-Type-Options.
  • Content-Security-Policy.
  • SSL Configuration Issues:
  • SSL forward secrecy not enabled.
  • weak / insecure cipher suites.
  • SPF, DKIM, DMARC issues.
  • Reporting older versions of any software without proof of concept or working exploit.
  • Systems and protocols that can be used in DDoS or DoS attacks.
  • reports that can be considered a beg bounty will not be processed nor responded to.

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 6 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.