Skip to content
KAGETERM

$ ./bug-hunt --target kageterm.com

Bug Hunt

Last updated: status: in effect

Found a security vulnerability or a bug in KAGETERM? Tell us. We will prioritize your report, fix the issue, and thank you. The finder of every confirmed issue can be added to the Hall of Fame.

Find

Test with your own account and follow the rules.

Report

Send the details to support@kageterm.com.

Confirm

We review the finding, set its severity, and get back to you.

Get listed

Once the fix is live, your name goes on the Hall of Fame.

Priority levels

We send a first reply to every report within 3 business days. The level depends on the impact of the finding.

  • CriticalHandled immediately

    Access to other users' accounts or data, authentication bypass, code execution on the server.

  • HighPrioritized

    Pro access without paying, privilege escalation, stored XSS.

  • MediumNext release

    Manipulating the leaderboard or points, bypassing rate limits, CSRF.

  • LowScheduled

    Low-impact misconfiguration, error messages that leak information, visual or functional bugs.

How to report

A good report gets confirmed fast. Include these in your email:

support@kageterm.com
title:
One-sentence summary of the issue
target:
The affected page or endpoint
steps:
What to do, in order, to reproduce it
impact:
What an attacker could do with it
proof:
Screenshot, sample request and response
name:
The name and link you want on the Hall of Fame (optional)

Send a reportsupport@kageterm.com

Scope

In scope

  • kageterm.com and its subdomains
  • Sign-in and session flow (GitHub, Google and Discord sign-in)
  • Account, progress, streak, and leaderboard data
  • Pro membership and post-payment authorization
  • Content bugs: a wrong command, a wrong explanation, a broken exercise

Out of scope

  • Denial of service (DoS, DDoS) and load testing
  • Social engineering, phishing, and physical attacks
  • Vulnerabilities in third-party services themselves (GitHub, Google, Discord, Supabase, Vercel, Cloudflare, the payment provider)
  • Automated scanner output and theoretical findings without proof
  • Issues that need an outdated browser, and missing-header reports without a demonstrated exploit
  • Actions that only affect your own account (such as self-XSS)

Rules of the hunt

  1. Test only with your own account and your own data. If you notice you have reached someone else's data, stop and report.
  2. Do not delete or change data, and do nothing that slows the service down.
  3. Keep the finding private until we have fixed it and told you.
  4. Do the minimum needed to prove the issue; do not keep any data you obtain.
  5. Follow applicable law.

Good-faith safe harbor

We treat research done in good faith and within these rules as authorized. We will not take legal action against you or close your account because of such research. Actions outside these rules are not covered.

What you get

  • We do not pay cash rewards at this time.
  • A personal thank-you and a permanent line on the Hall of Fame for every confirmed finding.
  • Critical and high findings are shown at the top of the list with the burning skull.
  • If several people report the same issue, the first reporter is listed.

Hall of Fame

The people who made KAGETERM safer. Added with the finder's consent once the finding is confirmed and the fix is live.

  1. #001 Viktor Ivanovski Practice progress reset when switching languages Low

Send a report