We take the security of Xperience seriously. If you believe you have found a security vulnerability, please report it to us as described below.
Please do not report security vulnerabilities through public GitHub issues.
Instead, please report them via email to [SECURITY_EMAIL_TO_BE_DEFINED] with the following information:
- Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.)
- Full paths of source file(s) related to the manifestation of the issue
- The location of the affected source code (tag/branch/commit or direct URL)
- Any special configuration required to reproduce the issue
- Step-by-step instructions to reproduce the issue
- Proof-of-concept or exploit code (if possible)
- Impact of the issue, including how an attacker might exploit it
- All code changes must go through a pull request review process
- At least one team member must review and approve changes before merging
- Security-critical changes require additional review
- Use of secure coding practices
- Regular dependency updates and security patches
- Automated security scanning in CI/CD pipeline
- Secret detection and prevention
- Two-factor authentication (2FA) is required for all team members
- Regular access review and cleanup of unused accounts
- Principle of least privilege for repository access
- Regular monitoring and updating of dependencies
- Automated vulnerability scanning of dependencies
- Manual review of security advisories
We release patches for security vulnerabilities. Below is our current supported versions:
| Version | Supported |
|---|---|
| 1.x.x | ✅ |
Security updates will be released as follows:
- The security team will review and validate the reported issue
- A fix will be prepared and tested
- A security advisory will be prepared
- The fix will be released and the advisory published
For additional security-related information, please contact [SECURITY_EMAIL_TO_BE_DEFINED].