Skip to content

Security: sseleman95/ClientProPlus

Security

SECURITY.md

Security Policy

If you believe you have found a security vulnerability in ClientPro+, please report it to us asap. The development team and community take all security issues seriously. Please do not make public any uncovered flaws.

Supported Versions

Versions of the project that are currently supported by security updates.

Version Supported
1.x.x

Reporting a Vulnerability

Thank you for improving the security of our code! Any assistance in removing security flaws will be acknowledged.

Please report security flaws by emailing the development team directly: sseleman95@gmail.com.

Include as much of the following information as possible to help us better understand the possible issue:

  • Type of issue (e.g. cross-site scripting)
  • 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
  • Impact of the issue, including how an attacker might exploit the issue

This information will help us triage your report more quickly.

The lead maintainer will acknowledge your email within 48 hours, and will send a more detailed response within 48 hours indicating the next steps in handling your report. After the initial reply to your report, the security team will endeavor to keep you informed of the progress towards a fix and full announcement, and may ask for additional information or guidance.

Disclosure Policy

When the security team receives a security bug report, they will assign it to a primary handler. This person will coordinate the fix and release process, involving the following steps:

  • Confirm the problem and determine the affected versions.
  • Audit code to find any potential similar problems.
  • Prepare fixes for all releases still under maintenance. These fixes will be released as fast as possible.

Comments on this Policy

If you have suggestions on how this process could be improved please submit a Pull Request.

Thank you in advance.

There aren’t any published security advisories