CVE-2026-131582: PagBank / PagSeguro e Vindi para WooCommerce <= 5.1.6 - Unauthenticated Stored Cross-Site Scripting via 'customer.name' Parameter

Published Nov 20, 2026
·
Updated

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.

Affected Software

1 affected component
PagBank PagBank / PagSeguro e Vindi para WooCommerce<=5.1.6

Event History

Nov 20, 2026
CVE Published
via MITRE·07:53 AM
Data Sourced
via MITRE·07:53 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·08:18 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which installations are affected?

All versions of the PagBank / PagSeguro e Vindi para WooCommerce WordPress plugin up to and including 5.1.6 are affected.

2

Does exploitation require an authenticated WordPress account or user interaction?

No. The vulnerability can be exploited by an unauthenticated attacker, and the affected vector is network-accessible with low attack complexity. A user must later access a page containing the injected payload for the stored script to execute.

3

How can an attacker plant the malicious payload?

An attacker can enter a script payload as the customer name during PagBank's legitimate hosted-checkout (Checkout PB) flow; no hash brute-forcing is required for this path. The woocommerce_api_rm_ps_notif webhook path is also exploitable because it relies only on a 5-character truncated wp_hash() value that can be brute-forced.

4

What is the potential impact if the issue is exploited?

Injected scripts can execute in the browser of users who visit an affected injected page. The published severity vector indicates low confidentiality and integrity impact, with no availability impact.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203