We actively maintain and provide security patches for the following versions of Rentify Frontend:
| Version | Supported |
|---|---|
| 1.x | Yes |
| < 1.0 | No |
The Rentify engineering team takes the security of our platform and user data seriously. If you discover a potential vulnerability or security flaw, please report it responsibly.
Do not create public GitHub issues for security vulnerabilities.
Instead, please submit a report directly via:
- Email: security@rentify.ua or directly to the project maintainer at polichdev@gmail.com
- GitHub: Use the private Security Advisory reporting feature.
To help us triage and resolve the issue quickly, please provide:
- A detailed description of the vulnerability.
- Step-by-step reproduction instructions or a minimal Proof of Concept (PoC).
- The potential impact (e.g., token exfiltration, XSS injection, unauthorized booking mutation).
- Any proposed fixes or mitigations.
- Initial Response: Within 48 hours.
- Triage & Status Update: Within 5 business days.
- Remediation Release: Depending on severity, critical patches will be prioritized and published within 7 days.
Rentify Frontend adheres to strict client-side security measures:
- Zero XSS Exposure: Elimination of
dangerouslySetInnerHTML, auto-escaping by React 19 JSX runtime, and strict form input sanitization with Zod. - Token Protection: Support for
HttpOnly; Secure; SameSite=Strictcookies in production mode to prevent JavaScript access to access and refresh tokens. - CSRF Protection: Implementation of Double-Submit CSRF cookie validation for all non-safe HTTP methods (
POST,PUT,DELETE). - Dependency Auditing: Automated continuous auditing via
npm audit --omit=dev --audit-level=high.