| Version | Supported |
|---|---|
| 1.4.x | ✅ Active support |
| < 1.4 | ❌ No longer supported |
If you discover a security vulnerability in Open Short URL, please report it responsibly. Do not open a public issue.
- Email: Send details to supra126@gmail.com
- Subject:
[SECURITY] <brief description> - Include:
- Description of the vulnerability
- Steps to reproduce
- Affected version(s)
- Potential impact
- Suggested fix (if any)
- Acknowledgment: Within 48 hours of your report
- Status update: Within 7 days with an assessment
- Resolution: Security patches are prioritized and released as soon as possible
The following are in scope for security reports:
- Authentication & authorization bypasses
- SQL injection, XSS, CSRF, SSRF
- Sensitive data exposure
- URL redirect manipulation
- API key / webhook secret leakage
- Rate limiting bypasses
- OIDC/SSO vulnerabilities
- Docker image vulnerabilities
- Vulnerabilities in third-party dependencies (report to the upstream project)
- Social engineering attacks
- Denial of service (DoS) attacks
- Issues in demo/staging environments
- Always use HTTPS (Caddy profile provides built-in SSL)
- Set strong
JWT_SECRETandENCRYPTION_KEYvalues - Enable 2FA for admin accounts
- Restrict CORS origins in production (
CORS_ORIGINS) - Use environment variables for all secrets — never commit
.envfiles - Keep your instance updated to the latest version
- Enable rate limiting in production
- Use a dedicated PostgreSQL user with minimal privileges
We appreciate responsible disclosure and will credit reporters in release notes (unless you prefer to remain anonymous).