phpmyadmin.net
External Program
Submit bugs directly to this organization
External Program
Submit bugs directly to this organization
We take any security issues found in our code seriously. On the right side, you can see past security issues that were discovered and fixed. For critical issues, we publish a security release (whose number contains a fourth digit like 3.3.10.5). See our https://docs.phpmyadmin.net/en/latest/security.html for more details about our security policy.
Should you find a security issue in the phpMyAdmin programming code, please contact the [mailto:[email protected]](phpMyAdmin security team) in advance before publishing it. This way we can prepare a fix and release the fix together with your announcement. You will be also given credit in our security announcement.
You can optionally encrypt your report with PGP key ID DA68AB39218AB947 with following fingerprint:
pub 4096R/DA68AB39218AB947 2016-08-02 Key fingerprint = 5BAD 38CF B980 50B9 4BD7 FB5B DA68 AB39 218A B947 uid phpMyAdmin Security Team [email protected] sub 4096R/5E4176FB497A31F7 2016-08-02
The key can be either obtained from the keyserver or is available in [https://files.phpmyadmin.net/phpmyadmin.keyring](phpMyAdmin keyring) available on our download server or using https://keybase.io/phpmyadmin_sec.
Should you have suggestion on improving phpMyAdmin to make it more secure, please report that to our [https://github.com/phpmyadmin/phpmyadmin/issues](issue tracker). Existing improvement suggestions can be found by [https://github.com/phpmyadmin/phpmyadmin/labels/hardening](hardening label).
Please note that any support requests sent to this address will not be answered; you should use the standard support methods mentioned on the /support/ page.
To follow the latest security releases, you can use an [/security/feed/](RSS feed).
2025 3
2023 1
2022 2
2020 6
2019 5
2018 8
2017 9
2016 71
2015 6
2014 18
2013 15
2012 7
2011 20
2010 10
2009 6
2008 10
2007 8
2006 9
2005 9
2004 4
2003 1