Title: Security handling
Last modified: April 19, 2022

---

# Security handling

 *  [B](https://wordpress.org/support/users/blclda/)
 * (@blclda)
 * [4 years, 1 month ago](https://wordpress.org/support/topic/security-handling/)
 * Hi, possible future user here, given that as recently as a month ago revoluts
   own official plugin was closed off the store after an SQL vulnerability was found,
   see here: [https://patchstack.com/database/vulnerability/revolut-gateway-for-woocommerce/wordpress-revolut-gateway-for-woocommerce-plugin-3-1-1-sql-injection-sqli-vulnerability](https://patchstack.com/database/vulnerability/revolut-gateway-for-woocommerce/wordpress-revolut-gateway-for-woocommerce-plugin-3-1-1-sql-injection-sqli-vulnerability)
 * What teps dos paybird take when it comes to plugin security? Is the code audited
   by an external company? Have you considered [https://patchstack.com/auditing/](https://patchstack.com/auditing/)
   as a possible option? It would make me more confident in adopting your plugin.

The topic ‘Security handling’ is closed to new replies.

 * ![](https://ps.w.org/paybyrd/assets/icon-256x256.jpg?rev=3047109)
 * [Paybyrd](https://wordpress.org/plugins/paybyrd/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/paybyrd/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/paybyrd/)
 * [Active Topics](https://wordpress.org/support/plugin/paybyrd/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/paybyrd/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/paybyrd/reviews/)

 * 0 replies
 * 1 participant
 * Last reply from: [B](https://wordpress.org/support/users/blclda/)
 * Last activity: [4 years, 1 month ago](https://wordpress.org/support/topic/security-handling/)
 * Status: not resolved