🔐

Report a Security Issue

Help us keep crenvu.com safe. We review every legitimate report from the security community and work to resolve valid issues quickly.

📅 Last Updated: August 2026 🤝 Responsible Disclosure
1

Responsible Disclosure

If you've found a security vulnerability affecting crenvu.com, we want to hear from you. We take all legitimate reports seriously and are committed to working with the security research community to identify and resolve issues responsibly.

🙏
Thank You We appreciate the time and effort researchers put into responsibly disclosing vulnerabilities. Reports that follow the ground rules below help us protect our customers faster — and we're grateful for it.
2

Ground Rules for Researchers

If you follow these principles when researching and reporting a security issue, we will not pursue legal action against you for your report:

  • Give us reasonable time to investigate and fix an issue before disclosing it publicly or to others.
  • Act in good faith — avoid privacy violations, service disruption, or destruction of data.
  • Only test against your own account. Do not access, modify, or attempt to access another customer's account or data.
  • Do not exploit the issue beyond what's needed to demonstrate the vulnerability.
  • Comply with all applicable laws throughout your research and disclosure process.
3

How to Report

Send your report directly to our team at Contact@crenvu.com with the subject line "Security Report." Please do not disclose the issue publicly or on social media before we've had a reasonable opportunity to investigate and address it.

4

What to Include

To help us investigate quickly, please include as much of the following as possible:

  • A clear description of the vulnerability and its potential impact
  • Step-by-step instructions to reproduce the issue
  • Screenshots, screen recordings, or proof-of-concept code, where relevant
  • The URL, endpoint, or feature affected
  • Any tools or browser/device details used during testing
Report quality matters. Reports without clear reproduction steps may take longer to investigate, and issues we're unable to reproduce cannot be validated. Vague or automated-scanner-only reports without confirmed exploitability are typically not actionable.
5

Bounty Rewards

We offer bounties to researchers who report valid, in-scope vulnerabilities, awarded at Crenvu LLC's discretion based on severity and impact. The first valid report of a given issue receives the bounty, and detailed, fully reproducible reports are required to qualify.

Critical
$200
  • Remote code execution
  • Full account takeover
  • SQL injection exposing data
  • Authentication bypass
High
$100
  • Sensitive data exposure
  • Stored XSS affecting others
  • Insecure session/cookie handling
Medium
$50
  • Business logic flaws
  • Insecure direct object references
Low
Recognition
  • Open redirects
  • Reflected XSS
  • Low-sensitivity info leaks
📋
Report Quality Matters Rewards are assessed based on impact, exploitability, and clarity of the report. Vague or unreproducible reports are not eligible for a bounty.
6

Out of Scope

The following are generally not considered actionable security reports:

Clickjacking on pages with no sensitive actions
Missing security headers without a demonstrated exploit
Vulnerabilities in third-party services we don't control
Automated scanner output with no confirmed impact
Social engineering of staff or customers
Denial-of-service or brute-force attacks
Issues already known and being addressed
Best-practice suggestions with no security impact
7

Contact Us

To submit a report or ask a question about this policy, reach out below.

Crenvu LLC — Security Team

All reports are reviewed promptly by our team.

🕐
Business HoursMon – Sat: 9:00 AM – 6:00 PM CST
Sunday: Closed
Note: Bounty payouts are issued at Crenvu LLC's discretion after review and validation of a qualifying report.