SC-CPE Security

We take security seriously. If you find a vulnerability, we want to hear about it.

Scope

In scope

  • Certificate forgery / revocation bypass
  • Audit log tampering or chain-break
  • Auth bypass on /api/admin/* or /api/me/*
  • Cross-user data leakage (dashboard token, cert, attendance)
  • XSS / injection reaching the verify portal or PDF issuer
  • CSRF on state-changing endpoints
  • Rate limit bypass or amplification
  • Information disclosure (PII, secrets, stack traces)

Out of scope

  • Denial of service without amplification
  • Clickjacking on non-sensitive pages
  • Best-practice header nits without exploit path
  • Theoretical timing attacks on high-entropy tokens
  • Social engineering / phishing of users or admins
  • Attacks requiring physical access

Rules of engagement

Response SLA

StageTimeline
Acknowledgement3 business days
Triage + initial assessment7 business days
Fix or mitigation (P0/P1)30 days

Recognition

We don't run a paid bug bounty. Researchers who report valid findings are credited below and in the repo's SECURITY.md. Tell us how you'd like to be credited in your report.

Hall of Fame

Be the first to find a vulnerability and earn your place here.

Defense posture

What you're up against. Source is public — we're not hiding behind obscurity.

Resources

This site runs on Cloudflare Pages + Workers + D1. The full source is public. All certificates are PAdES-T signed with a hash-chained audit log. See DESIGN.md for architecture.