Currently supported versions for security updates:
| Version | Supported |
|---|---|
| 1.0.x | ✅ |
| < 1.0 | ❌ |
We take the security of ReplyPilot AI seriously. If you discover a security vulnerability, please follow these steps:
- Create a public GitHub issue
- Share vulnerability details in public forums
- Include personally identifiable information (PII) in reports
- Include actual logs containing sensitive data
- Email us directly: Send vulnerability reports to support@fluentthemes.com
- Include details:
- Type of vulnerability
- Steps to reproduce
- Potential impact
- Suggested fix (if any)
- Allow time: We aim to respond within 48 hours
ReplyPilot AI implements multiple security layers:
- CSRF Protection: All forms include token validation
- SQL Injection Prevention: PDO prepared statements
- XSS Protection: Input sanitization and output escaping
- Session Security: Secure session handling with timeout
- Access Control: Admin authentication middleware
- Rate Limiting: Built-in API endpoint protection
- Change default tokens: Always update the installer token after setup
- Use strong passwords: Enforce complex admin passwords
- Keep updated: Regularly update PHP and dependencies
- Enable HTTPS: Always use SSL/TLS in production
- Review logs: Monitor access and error logs regularly
- Restrict access: Limit admin panel access by IP when possible
Recommended security headers for production:
Header set X-Content-Type-Options "nosniff"
Header set X-Frame-Options "SAMEORIGIN"
Header set X-XSS-Protection "1; mode=block"
Header set Referrer-Policy "strict-origin-when-cross-origin"Security Contact: support@fluentthemes.com Response Time: 24-48 hours