Cloud Linux Software, Inc.
Vulnerability disclosure program on security.txt cloudlinux.com
- Top reward
- No cash rewards
- Top severity paid
- Not published
- Assets in scope
- 4
- Public CVEs
- 0
- Last change
- No changes yet
At a glance
What to know before you start testing.
- No cash rewards
- A disclosure program: you report for credit, not money.
- Report by email
- [email protected]
- Full safe harbor
- Good-faith research is authorised; no legal action.
- Replies within 3 days
- As the policy promises.
- Publish after a fix
- Coordinate the timing with the company.
Rewards
What the company's own policy page says it pays.
This program does not pay cash rewards.
- Response
-
Within 3 days
We will make a best effort to provide a non-automated acknowledgment of your report’s receipt within 3 business days .
- Safe harbor
-
Full
We consider security research activities conducted under this policy to be “authorized” and will not pursue civil or criminal action against any party for good-faith research that adheres to this policy.
- Hall of fame
-
Yes
While we do not operate a formal bug bounty program, we are happy to provide public recognition (with your permission) to researchers who contribute to the security of our platform.
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
4 assets you may test.
Domains 2
- cloudlinux.com
- imunify360.com
Products and areas 2
- CloudLinux products
- company services and systems
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Cloud Linux Software, Inc.'s policy. "We" in these lines means the program, not this site.
While testing
-
Make every effort to avoid privacy violations, degradation of user experience, disruption to production systems, and destruction or manipulation of data.
-
Only use exploits to the extent necessary to confirm a vulnerability’s presence.
-
Provide us with a reasonable amount of time to remediate the issue before public disclosure.
Not accepted
-
Clickjacking on pages with no sensitive actions
-
Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions
-
Attacks requiring MITM or physical access to a user’s device
-
Previously known vulnerable libraries without a working Proof of Concept
-
Comma-Separated Values (CSV) injection without demonstrating a vulnerability
-
Missing best practice, configuration, or policy suggestions, including SSL/TLS configurations that do not contain a fully functional proof-of-concept
-
Missing/enabled HTTP header/methods that do not lead directly to a security vulnerability
-
Any activity that could lead to the disruption of our service (DoS)
-
Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
-
Rate limiting or brute-force issues on non-authentication endpoints
-
Missing best practices in Content Security Policy
-
Missing HttpOnly or Secure flags on insensitive cookies
-
Missing email best practices (Invalid, incomplete, or missing SPF/DKIM/DMARC records, etc.)
-
Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g, stack traces, application or server errors)
-
Tabnabbing
-
Open redirect – unless an additional security impact can be demonstrated
-
Issues that require unlikely user interaction
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 3 hours ago.
No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.
Public CVEs
Published vulnerabilities in this vendor's products, from the NVD.
No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.