| Version | Supported |
|---|---|
1.x |
✅ |
Security fixes are applied to the latest release on the default branch (master / main).
Please do not report security vulnerabilities through public GitHub Issues.
If you discover a security issue in this theme starter, report it privately:
- Open a GitHub Security Advisory on this repository, or
- Report via the ReactPress main repository if the issue affects the broader platform or toolkit.
Include as much detail as possible:
- Description of the vulnerability and potential impact
- Steps to reproduce
- Affected routes, components, or configuration
- Suggested fix (if any)
We aim to acknowledge reports within 5 business days and will coordinate disclosure once a fix is available.
This policy covers this repository (the Next.js theme frontend). Issues in the ReactPress API, admin console, or @fecommunity/reactpress-toolkit should be reported to the ReactPress project.
- Cross-site scripting (XSS) in theme-rendered content or components
- Open redirects in theme routing or auth flows
- Sensitive data exposure via misconfigured environment variables documented in this repo
- Insecure defaults in theme scripts or mock API handlers
- Vulnerabilities in third-party CMS content uploaded by site operators
- Server-side issues in the ReactPress NestJS API (report upstream)
- Denial-of-service against a self-hosted deployment without a demonstrated theme-level flaw
Contributors should:
- Never commit secrets (
.env, tokens, private keys) - Use
.env.examplefor documentation-only defaults - Run
pnpm run checkbefore opening pull requests - Follow CONTRIBUTING.md for review and testing expectations
Thank you for helping keep ReactPress themes safe for everyone.