Help us keep SimplAI secure by responsibly disclosing security vulnerabilities
| Category | Category Examples (non‑exhaustive) |
|---|---|
| Informational disclosures | Software banners, stack traces, generic server errors |
| Legacy‑browser issues | Bugs affecting only obsolete browsers |
| Service‑abuse findings | Rate‑limiting gaps, generic brute‑force or DoS weaknesses |
| Defense‑in‑depth gaps | Missing security headers, cookie attributes, or restrictive HTTP methods |
| DNS hygiene | Missing or misconfigured CAA, SPF, DMARC, DKIM, MTA‑STS records |
| UI quirks | Clickjacking/tab‑nabbing on non‑sensitive pages |
| Low‑impact CSRF | CSRF on unauthenticated or non‑sensitive actions |
| Minor client‑side issues | Prototype pollution, clear‑text password submission, private‑IP disclosure, unencrypted non‑sensitive traffic |
| Host‑header injection | Unless it demonstrably leads to a security impact |