CVE-2026-131582 json
PagBank / PagSeguro e Vindi para WooCommerce <= 5.1.6 - Unauthenticated Stored Cross-Site Scripting via 'customer.name' Parameter
published yesterday modified yesterday also EUVD-2026-131121
- cvss
- 7.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 47%
- public exploits
- 0
- none known
Summary
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.
Is CVE-2026-131582 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- yesterday
Exploit prediction
0.56% chance of exploitation in the next 30 days, higher than 47% of all scored CVEs (FIRST EPSS, 2026-11-21).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.2 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N |
Affected products
- martins56 PB Integrações (antigo PagBank Integrações) para WooCommerce
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/d783a925-fb9a-490c-8b04-ade67c587fc8?source=cve
- plugins.trac.wordpress.org /browser/pagbank-connect/tags/5.1.6/src/Connect/Recurring/Admin/Subscriptions/SubscriptionDetails.php#L79
- plugins.trac.wordpress.org /browser/pagbank-connect/tags/5.1.6/src/Connect/Recurring/Admin/Subscriptions/SubscriptionDetails.php#L103
- plugins.trac.wordpress.org /browser/pagbank-connect/tags/5.1.6/src/Traits/ProcessPayment.php#L716
- plugins.trac.wordpress.org /browser/pagbank-connect/tags/5.1.6/src/Traits/ProcessPayment.php#L354
- plugins.trac.wordpress.org /browser/pagbank-connect/tags/5.1.6/src/Connect.php#L57
- plugins.trac.wordpress.org /changeset?reponame=&old=3808657%40pagbank-connect&new=3808657%40pagbank-connect
Sources
- CVE List CVE-2026-131582
- NVD CVE-2026-131582
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.