Skip to content

Security: hyperpolymath/wp-plugin-conflict-mapper

SECURITY.md

Security Policy

Supported Versions

We release patches for security vulnerabilities for the following versions:

Version Supported
1.0.x
< 1.0

Reporting a Vulnerability

Please do not report security vulnerabilities through public GitHub issues.

How to Report

  1. Email: Send details to security@hyperpolymath.com (or create a security contact if needed)
  2. Encryption: Use PGP if possible (key available in .well-known/security.txt)
  3. Response Time: We aim to acknowledge within 48 hours
  4. Disclosure Timeline: We follow coordinated disclosure (90 days)

What to Include

Please include the following information:

  • Type of vulnerability
  • Full paths of source file(s) related to the vulnerability
  • Location of the affected source code (tag/branch/commit or direct URL)
  • 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

Security Scanning

This plugin has been designed with security as a priority:

Input Validation: All user inputs sanitized using WordPress functions ✅ Output Escaping: All outputs escaped to prevent XSS ✅ SQL Injection Prevention: Prepared statements via wpdb ✅ Nonce Verification: All AJAX requests verified ✅ Capability Checks: All admin functions require manage_optionsCSRF Protection: WordPress nonces on all forms ✅ File Operation Security: No direct file system access from user input ✅ No eval(): No dynamic code execution ✅ Secure Defaults: All settings default to secure values

Security Features

Built-in Security Scanner

The plugin includes a security scanner that checks for:

  • Dangerous function usage (eval, exec, system, etc.)
  • SQL injection vulnerabilities
  • XSS risks
  • Insecure file operations

OWASP Top 10 Protections

We specifically protect against:

  1. A01:2021 – Broken Access Control: Capability checks on all operations
  2. A02:2021 – Cryptographic Failures: No sensitive data storage
  3. A03:2021 – Injection: Prepared statements, input sanitization
  4. A04:2021 – Insecure Design: Secure-by-default architecture
  5. A05:2021 – Security Misconfiguration: Secure default settings
  6. A06:2021 – Vulnerable Components: Minimal dependencies
  7. A07:2021 – Authentication Failures: WordPress auth integration
  8. A08:2021 – Data Integrity Failures: Nonce verification
  9. A09:2021 – Logging Failures: WordPress debug logging
  10. A10:2021 – SSRF: No external URL fetching from user input

Security Hardening

For Administrators

  1. Keep Updated: Always use the latest version
  2. Limit Access: Only administrators should have access
  3. Monitor Scans: Review security scan results regularly
  4. Audit Logs: Check WordPress logs for suspicious activity
  5. Database Backups: Regular backups before running scans

For Developers

  1. Code Review: All PRs require security review
  2. Static Analysis: Use PHPCS with WordPress security standards
  3. Dependency Scanning: Minimal dependencies by design
  4. Secure Coding: Follow WordPress VIP coding standards
  5. Security Testing: Test all inputs with malicious payloads

Vulnerability Disclosure Policy

Our Commitment

  • We will respond to your report within 48 hours
  • We will keep you informed of our progress
  • We will credit you in our security advisories (unless you prefer anonymity)
  • We will not take legal action against security researchers acting in good faith

What We Expect

  • Give us reasonable time to fix the vulnerability before public disclosure
  • Do not access, modify, or delete data without permission
  • Do not perform DoS or DDoS attacks
  • Do not exploit the vulnerability beyond what's necessary for demonstration

Security Updates

Security updates are released as soon as possible after a vulnerability is verified and patched. Updates are distributed through:

  • WordPress.org plugin repository (if published)
  • GitHub releases
  • Security mailing list (if subscribed)

Compliance

This plugin aims to comply with:

  • WordPress Security Best Practices
  • OWASP Top 10
  • CWE Top 25 Most Dangerous Software Weaknesses
  • GDPR (no personal data collection by default)
  • WCAG 2.1 AA (accessible admin interface)

Security Audit History

Date Auditor Scope Findings Status
2025-07-31 Internal Initial Release 0 critical, 0 high Resolved

Hall of Fame

We recognize security researchers who have responsibly disclosed vulnerabilities:

No vulnerabilities reported yet

Contact

References

There aren’t any published security advisories