Security is a top priority at Piwik. As potential issues are discovered, we validate, patch and release fixes as quickly as we can.
We have a security bug bounty program in place that rewards researchers for finding security issues and disclosing them to us. We also document here how you can make your own Piwik data safer and secure your server.
Please subscribe to the Changelog to be notified of new releases (including security releases).
The Piwik Security Bug Bounty Program is designed to encourage security research in Piwik software and to reward those who help us create the safest web analytics platform.
The bounty for valid critical security bugs is a $500 (US) cash reward. The bounty for non-critical bugs is $200 (US), paid via Paypal.
Since we started this program in Jan 2011, we have already rewarded more than 15 researchers. This program has been very successful in improving code quality and fixing all known security issues in Piwik.
The bounty will be awarded for security bugs that meet the following criteria:
We also maintain a list of requests for security improvements.
Please email security issues to firstname.lastname@example.org. Please provide as much detail as you can about your environment, Piwik version, plugins used (if relevant), and any other relevant information.
You will receive a response from a team member acknowledging receipt of your email, typically within 24 hrs. If you do not receive a response, please do not assume we’re ignoring you – it’s quite possible your email didn’t make it through a spam filter.
We appreciate your patience and input. Some bugs take time to correct and the process may involve a review of the codebase for similar problems. Coordinating across time zones and work schedules can be time-consuming. Please do not disclose the vulnerability to anyone until a few days after the release of the stable Piwik, and after the advisory is issued.
Core developers are all committed to achieving the highest standard of security. All Piwik PHP code should adhere to the security checklist. All commits to the Piwik Git repository are reviewed by at least two core developers.
We hope Piwik is not vulnerable to any critical security bugs, and we are committed to ensuring that this is the case. Thank you for your support!
Once you have installed Piwik and started gathering visitor data in your MySQL database, you may be concerned about others accessing your server. There are easy steps you can take to ensure that adding Piwik in your existing software environment (CMS, CRM, etc.) will be as safe as possible.
Installing Piwik and tracking visitors is quick and easy, but how can you make sure it is nearly impossible to hack into your server, or protect your database data from being accessed by external parties?
To make your server & database more secure, check out our step by step guide: Secure Piwik server: steps to keep Piwik safe
We recommend to Turn on automatic SSL redirection in your Piwik.
Piwik strives to provide excellent Privacy features for you, the Piwik user, but also to the visitors being tracked in your Piwik. See the Piwik & User Privacy for more information.