CVE-2026-131582
High 7.2No known exploitationFix status unknownTitle not yet published
Record last updated
CVSS score
High on a 0 to 10 scale
EPSS, chance of exploitation in 30 days
Higher than 39% of scored CVEs. A prediction, not evidence.
CISA remediation deadline
Not in the KEV catalog
Description
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 woocommerce_api_rm_ps_notif webhook path is additionally exploitable because its only gate is a 5-character (20-bit) truncated wp_hash() that is trivially brute-forceable.
Weakness: CWE-79
Patching and mitigation
- Patch status
- Unknown: no source documents a fix
- Mitigation
- None documented
- Vendor guidance
- No vendor link on record
Affected products
No affected products documented yet.
Timeline
- No dated events documented yet.
Vendor guidance and references
- https://plugins.trac.wordpress.org/browser/pagbank-connect/tags/5.1.6/src/Connect.php (opens in a new tab)
- https://plugins.trac.wordpress.org/browser/pagbank-connect/tags/5.1.6/src/Connect/Recurring/Admin/Subscriptions/SubscriptionDetails.php (opens in a new tab)
- https://plugins.trac.wordpress.org/browser/pagbank-connect/tags/5.1.6/src/Traits/ProcessPayment.php (opens in a new tab)
- https://plugins.trac.wordpress.org/changeset?reponame=&old=3808657%40pagbank-connect&new=3808657%40pagbank-connect (opens in a new tab)
- https://www.wordfence.com/threat-intel/vulnerabilities/id/d783a925-fb9a-490c-8b04-ade67c587fc8?source=cve (opens in a new tab)