Skip to main content
CVE-2026-131582VulnerabilityPublished

The PagBank / PagSeguro e Vindi para WooCommerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-131582· High 7.2

Not known to be exploited · CVSS 7.2 High.

Data as of 20 Nov 2026, 10:48 UTC

CVSS 3.1 base score
7.2High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Wordfence)CVSS 3.17.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
martins56PB Integrações (antigo PagBank Integrações) para WooCommerceAffected
  • <=5.1.6
Fixed in–

AI-suggested

Until a fix is released, users should consider disabling or restricting access to the affected plugin features, especially the webhook endpoint and hosted-checkout flow. Monitoring for suspicious activity related to these components is advisable.

Description

The PagBank / PagSeguro e Vindi para WooCommerce plugin for WordPress contains a stored cross-site scripting (XSS) vulnerability in the 'customer.name' parameter. This affects all versions up to and including 5.1.6. The vulnerability allows unauthenticated attackers to inject arbitrary scripts that execute when users access the affected pages. The injection can be performed via the hosted-checkout flow by submitting malicious input as the customer name. Additionally, the webhook path 'woocommerce_api_rm_ps_notif' is vulnerable due to a weak 5-character truncated wp_hash() protection that can be brute-forced easily.

References

Community reviews

Loading reviews…