See how pagbank compares to other vendors in security performance
The PagBank / PagSeguro e Vindi para WooCommerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'customer.name' parameter in all versions up to, and including, 5.1.6 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The payload can be planted via the legitimate hosted-checkout (Checkout PB) flow simply by entering it as a customer name on PagBank's payment page, requiring no hash brute-forcing whatsoever; the woocommerceapirmpsnotif webhook path is additionally exploitable because its only gate is a 5-character (20-bit) truncated wphash() that is trivially brute-forceable.
The PagBank / PagSeguro Connect para WooCommerce plugin for WordPress is vulnerable to SQL Injection via the 'status' parameter in all versions up to, and including, 4.44.3 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Shop Manager-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.