| Version | Supported |
|---|---|
| 1.x.x | ✅ |
| < 1.0 | ❌ |
We take security seriously. If you discover a security vulnerability in PostXAgent, please report it responsibly.
- DO NOT create a public GitHub issue for security vulnerabilities
- Email the maintainers directly or use GitHub's private vulnerability reporting feature
- Include as much detail as possible:
- Type of vulnerability
- Steps to reproduce
- Potential impact
- Suggested fix (if any)
- Acknowledgment: We will acknowledge receipt within 48 hours
- Assessment: We will assess the vulnerability and its impact
- Resolution: We aim to release a fix within 7-14 days for critical issues
- Disclosure: We will coordinate with you on public disclosure timing
The following are in scope for security reports:
- Laravel Backend (PHP)
- AI Manager Core (C#)
- AI Manager API
- AI Manager UI
- Authentication/Authorization issues
- Data exposure vulnerabilities
- API security issues
- Social media platform security (report to respective platforms)
- Third-party AI provider security (report to respective providers)
- Issues in dependencies (report to upstream maintainers)
When deploying PostXAgent:
- Environment Variables: Never commit
.envfiles or API keys - HTTPS: Always use HTTPS in production
- Updates: Keep all dependencies up to date
- Access Control: Implement proper access controls for the admin panel
- API Keys: Rotate API keys regularly
- Monitoring: Monitor for unusual activity
We appreciate the security research community's efforts in helping keep PostXAgent secure. Contributors who report valid security issues will be acknowledged (if they wish) in our release notes.