Skip to content
bugbounty.fyi
Get paid to secure open source 475 paid open-source programs on Sorona, up to $1M Perk Low bugs: $100 or 1 mo Claude Max

Also on Patchstack. All 476 paid open-source programs

Try

Highest paying Newly launched Paid without KYC Full safe harbor
All results

About this site

Plausible Analytics

Vulnerability disclosure program on security.txt plausible.io

Accepting reports Full safe harbor security.txt
Go to program Website
Top reward
No cash rewards
Top severity paid
Not published
Assets in scope
3
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 5 days
As the policy promises.
No public write-ups
Keep findings private.

Rewards

What the company's own policy page says it pays.

This program does not pay cash rewards.

Response
Within 5 days We will respond within 1 to 5 working days.
Safe harbor
Full Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you.

Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original

Scope

3 assets you may test, 30 excluded.

Domains 1

  • plausible.io

Source code 1

  • https://github.com/plausible/analytics

Wildcard domains 1

  • *.plausible.io
Out of scope (30)
  • 0-day vulnerabilities less than 30/60/90 days from patch release.
  • Attacks requiring MITM or physical access to a user’s device
  • Clickjacking/UI redressing
  • Content spoofing
  • CSRF/XSS with long or unpredictable parameter
  • Distributed Denial of Service attacks that require large volumes of data.
  • Error information disclosure that cannot be used to make a direct attack
  • Feedback, comment, message, etc. flooding
  • Flash-based vulnerabilities
  • Information leakage that cannot be used to make a direct attack, like server IP, server version, path, error message, internal IP, etc.
  • Issues related to networking protocols or industry standards
  • Local denial of service of Mobile APP
  • Login/logout/unauthenticated/low-impact CSRF
  • Missing cookie flags
  • Missing security-related HTTP headers which do not lead directly to a vulnerability
  • Mixed content warnings
  • No SPF/DMARC in non-email domains/subdomains
  • Physical or social engineering attacks
  • PII - do not collect any personally identifiable information - including credit card information, addresses and phone numbers from other customers.
  • Provisioning and/or usability issues.
  • Reflected file download attacks (RFD)
  • Reports from automated tools or scans.
  • Security vulnerabilities in third-party products or websites that are not under Plausible Analytics’ direct control.
  • “Self” XSS
  • Session fixation
  • SMS/Email flooding for some of our business
  • Social engineering and physical attacks
  • SSL/TLS best practices
  • Unverified Results of automated tools or scanners
  • Violations of licenses or other restrictions applicable to any vendor’s product.

Rules

What the policy asks of you, and the bug types it won't reward, quoted from Plausible Analytics's policy. "We" in these lines means the program, not this site.

While testing

  • Please document your findings thoroughly, providing steps to reproduce and send your report to us.
  • You must be available to provide additional information if needed by us to reproduce and investigate the report.
  • By disclosing a vulnerability, you agree that you may not publicly disclose your findings or the contents of your submission to any third parties.

Not accepted

  • Information leakage that cannot be used to make a direct attack, like server IP, server version, path, error message, internal IP, etc.
  • PII - do not collect any personally identifiable information - including credit card information, addresses and phone numbers from other customers.
  • Reports from automated tools or scans.
  • Social engineering and physical attacks
  • Distributed Denial of Service attacks that require large volumes of data.
  • 0-day vulnerabilities less than 30/60/90 days from patch release.
  • Provisioning and/or usability issues.
  • Violations of licenses or other restrictions applicable to any vendor’s product.
  • Security vulnerabilities in third-party products or websites that are not under Plausible Analytics’ direct control.
  • “Self” XSS
  • Session fixation
  • Content spoofing
  • Missing cookie flags
  • SSL/TLS best practices
  • Mixed content warnings
  • Clickjacking/UI redressing
  • Flash-based vulnerabilities
  • Local denial of service of Mobile APP
  • Reflected file download attacks (RFD)
  • Physical or social engineering attacks
  • Feedback, comment, message, etc. flooding
  • SMS/Email flooding for some of our business
  • CSRF/XSS with long or unpredictable parameter
  • Login/logout/unauthenticated/low-impact CSRF
  • Unverified Results of automated tools or scanners

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.

Search NVD

No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.