We release patches for security vulnerabilities for the following versions:
| Version | Supported |
|---|---|
| 1.0.x | ✅ |
We take the security of Quick Customer module seriously. If you believe you have found a security vulnerability, please report it to us as described below.
- Open a public GitHub issue for security vulnerabilities
- Discuss the vulnerability in public forums or social media
-
Email us directly at security@sajdoko.com with:
- A description of the vulnerability
- Steps to reproduce the issue
- Potential impact
- Suggested fix (if you have one)
-
Give us reasonable time to address the issue before public disclosure (typically 90 days)
-
Act in good faith towards our users and the project
- Initial Response: Within 48 hours
- Status Update: Within 7 days
- Fix Timeline: Depends on severity
- Critical: Within 48 hours
- High: Within 7 days
- Medium: Within 30 days
- Low: Next scheduled release
When using this module:
- Keep Updated: Always use the latest version
- Restrict Permissions: Only give customer creation permission to trusted staff
- Monitor Logs: Regularly check Perfex CRM logs for suspicious activity
- Validate Input: The module validates input, but ensure your Perfex CRM is also updated
- Use HTTPS: Always use HTTPS in production environments
- This module respects Perfex CRM's staff permission system
- Customer creation requires
customers - createpermission - All inputs are sanitized using Perfex CRM's security functions
- CSRF protection is handled by Perfex CRM framework
- XSS protection via proper output escaping
Once a security vulnerability is fixed:
- We will release a patched version
- Update CHANGELOG.md with security fix notice
- Credit the reporter (if they wish) in release notes
- Publish a security advisory on GitHub
We recognize and thank security researchers who help keep our users safe:
- None yet - be the first!
Note: This security policy is subject to change. Please check back regularly for updates.
Last updated: October 26, 2025