Find the Flaw. Protect the Future.
We believe in open collaboration with global security researchers. Help us safeguard our learning infrastructure and student platform.
Safe Harbor & Responsible Disclosure
We commit not to pursue legal action against researchers acting in good faith within program scope.
Eligible Vulnerabilities & Severity Classes
Bounties and Hall of Fame recognition are awarded based on CVSS v3.1 impact criteria.
Remote Code Execution & Core Auth
RCE, SQLi leading to full database compromise, complete authentication bypass, or infrastructure takeover.
- SQL Injection / NoSQL Injection
- Remote Code Execution (RCE)
- Privilege Escalation to SuperAdmin
Broken Access Control & Stored XSS
BOLA / IDOR exposing PII of other students, Server-Side Request Forgery (SSRF), or stored cross-site scripting.
- IDOR exposing candidate profiles
- Stored Cross-Site Scripting (XSS)
- Server-Side Request Forgery (SSRF)
Reflected XSS & Session Risks
Reflected XSS, CSRF on state-changing actions, insecure session handling, or misconfigured CORS.
- Reflected Cross-Site Scripting
- Cross-Site Request Forgery (CSRF)
- Insecure Direct Object References (non-PII)
Info Leaks & Config Hygiene
Sensitive data exposures in error responses, mixed content, or missing non-critical security headers.
- Stack trace exposures
- CORS misconfigurations (read-only)
- Internal IP leak in headers
Program Scope & Target Assets
Please review the targets below before beginning testing. Attacks causing service denial or accessing user data without authorization violate program rules.
*.careersnova.in, api.careersnova.in, portal.careersnova.in
DoS/DDoS attacks, physical security, social engineering of employees or students, third-party hosted services (e.g. AWS, SendGrid).
Researcher Code of Conduct
- Do not access, modify, or delete any real student or partner data.
- Stop testing immediately if you encounter private user records and report findings.
- Provide reproducible Proof of Concept (PoC) steps with reasonable detail.
- Allow up to 30 days for remediation before disclosing findings publicly.
Submit Vulnerability Report
Submissions are encrypted and reviewed by our core SecOps engineering team.