Skip to main content

Security · Responsible disclosure

Report a security issue

VulnRadar is a security scanner, so we hold our own code to the same bar. If you have found a vulnerability, we want to hear about it before anyone else does. This page is the one place that tells you how to reach us, what we treat as in scope, and what you can expect once you hit send.

#Reporting a vulnerability

Email our security team with enough detail for us to reproduce the problem. If you would rather not email, the contact form reaches us too, but it delivers to the general support mailbox rather than this address, and it cannot carry an attachment. Email is faster and lets you send a proof of concept.

One report per issue is easier for both of us to track. If you found several unrelated problems, send them separately so each gets its own thread and its own fix.

#What to put in the report

The more of this you include, the faster we can confirm and fix it:

  • What the vulnerability is and what an attacker could actually do with it.
  • Step-by-step instructions to reproduce it, or a short proof-of-concept.
  • The affected URL, endpoint, or component, plus the version or commit SHA if you know it.
  • Whether you are testing the hosted service or a self-hosted deployment.
  • The name or handle you want credited, if you want credit at all.

#What happens next

You are not shouting into a void. Here is the timeline we hold ourselves to once a valid report lands:

We acknowledge your report
Within 48 hours
We send an initial assessment
Within 5 business days
We ship a fix
Depends on severity
We coordinate public disclosure
With you, typically around 90 days

If a report turns out to be a duplicate or out of scope, we will tell you that too, rather than leaving you guessing.

#In scope

Things we very much want reports about:

  • Authentication, authorization, and session handling.
  • Injection of any kind: XSS, SQL injection, SSRF, command injection.
  • Information disclosure: other users' PII, API keys, or scan results.
  • Rate-limit and quota bypasses.
  • Billing and Stripe integration bugs.
  • Scanner correctness: a check that misses a real vulnerability.
  • Self-hosted deployment security: Docker, secrets, environment variables.

#Out of scope

Reports we will most likely close without a fix:

  • Denial of service through large or expensive scan requests. We rate-limit those on purpose.
  • Issues in third-party services we do not control, such as Stripe itself.
  • Raw scanner output with no demonstrated impact.
  • Theoretical findings with no concrete attack path.
  • Self-hosted deployments that skip our hardening guide.
  • Missing security headers on pages that carry no sensitive data.

#Safe harbor

If you make a good-faith effort to follow this policy, we will treat your research as authorized. We will not pursue legal action against you or ask a third party to, and we will not report you to law enforcement for the testing itself.

Good faith means, concretely:

  • Test only against your own account and your own targets, never another user's data.
  • Stop as soon as you have confirmed a vulnerability, do not go digging further into real data.
  • Do not run attacks that degrade the service for others, such as sustained load or spam.
  • Give us a reasonable window to fix the issue before you tell anyone else.

This is not a paid bug bounty. We credit researchers who want it, but there is no cash reward.

#Coordinated disclosure

We disclose fixed issues publicly, and we would like you to be part of that. We aim to coordinate a disclosure date with you once a fix is out, usually around 90 days after the report, sooner for a small fix and longer for anything that needs a careful rollout.

The machine-readable version of this policy lives at /.well-known/security.txt, and the full written policy is in SECURITY.md in the repo, where you will also find how to verify a signed release.

VulnRadar is open source. Read the code, file non-security bugs, or open a pull request on GitHub. For anything that is not a security issue, use the contact page.

Security & Responsible Disclosure | VulnRadar