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

Piwik

By Matomo Bug bounty on Self-hosted matomo.org

Accepting reports
Go to program Website
Top reward
$13,000
Top severity paid
Critical
Assets in scope
2
Public CVEs
2
Last change
No changes yet

At a glance

What to know before you start testing.

Pays up to $13,000
for critical bugs.
Report by email
[email protected]
Partial safe harbor
Some legal protection; read the terms.
Replies within 1 day
As the policy promises.
Paid by PayPal
No identity requirement stated.
Publish after a fix
Coordinate the timing with the company.

Rewards

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

Severity Reward
Critical $13,000
Top reward
$13,000 The bounty for valid critical security bugs is a $13,000 (US) cash reward.
Response
Within 1 days A response from a team member acknowledging receipt of your email, will typically be within 24 hrs.
Safe harbor
Partial Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service.
Hall of fame
Yes As a thank you, your name will be credited in the Changelog

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

Scope

2 assets you may test, 23 excluded.

Domains 1

  • matomo.org

Web 1

  • https://builds.matomo.org/latest.zip
Out of scope (23)
  • Application Errors on pages
  • Blind Server-Side Request Forgery
  • Brute force, DoS, DDoS, phishing, text injection, or social engineering attacks.
  • Clickjacking
  • CLI is out out scope (including the Matomo console commands)
  • CORS related issues in any of our *.matomo.org websites.
  • Crime/beast attack and Lack of HTTP security headers (CSP, X-XSS, etc.)
  • HSTS or CSP headers
  • Information disclosure
  • Issues related to world writable files in a shared hosting environment
  • Missing cookie flags on non-sensitive cookies.
  • Open Directory Listing
  • Output from automated scans
  • Path disclosure
  • Race conditions to bypass limits/quotas.
  • Security issues as a result of running a Matomo instance without HTTPS
  • SPF, DMARC records missing
  • Users with super user privileges can post arbitrary JavaScript
  • Version disclosure
  • Vulnerabilities affecting users of outdated browsers or platforms.
  • Vulnerabilities caused by not applying Matomo security best practises
  • Vulnerabilities due to an older version of PHP, or MySQL (or MariaDB), or in the web server (Apache/Nginx), or Operating System (Linux/Windows).
  • Vulnerabilities in third party plugins (not authored by Matomo nor InnoCraft)

Rules

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

While testing

  • Let us know as soon as possible upon discovery of a potential security issue, and we’ll make every effort to quickly resolve the issue.
  • Provide us a reasonable amount of time to resolve the issue before any disclosure to the public or a third-party.
  • Reported security issues must be original and previously unreported
  • Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service.
  • Only interact with accounts you own or with explicit permission of the account holder.
  • Please don’t run automated tools against live servers without contacting us first.
  • Please don’t test contact forms and similar actions that send out emails
  • Please don’t sign up for more than one free trial on InnoCraft cloud.
  • Please submit any open source security issues directly to us, do not open security-related issues on public GitHub repositories.

Not accepted

  • Path disclosure
  • Clickjacking
  • Information disclosure
  • Version disclosure
  • Open Directory Listing
  • CORS related issues in any of our *.matomo.org websites.
  • Application Errors on pages
  • Crime/beast attack and Lack of HTTP security headers (CSP, X-XSS, etc.)
  • Security issues as a result of running a Matomo instance without HTTPS
  • Brute force, DoS, DDoS, phishing, text injection, or social engineering attacks.
  • Output from automated scans
  • Missing cookie flags on non-sensitive cookies.
  • Users with super user privileges can post arbitrary JavaScript
  • Vulnerabilities affecting users of outdated browsers or platforms.
  • Issues related to world writable files in a shared hosting environment
  • Race conditions to bypass limits/quotas.
  • Blind Server-Side Request Forgery
  • HSTS or CSP headers
  • SPF, DMARC records missing
  • Vulnerabilities due to an older version of PHP, or MySQL (or MariaDB), or in the web server (Apache/Nginx), or Operating System (Linux/Windows).
  • Vulnerabilities caused by not applying Matomo security best practises
  • Vulnerabilities in third party plugins (not authored by Matomo nor InnoCraft)
  • CLI is out out scope (including the Matomo console commands)

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 6 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
CVESeverityPublished
CVE-2014-5871 Medium 5.4 11 Sep 2014
CVE-2010-1453 Medium 4.3 7 May 2010