LearnCTEM.com, Best CTEM Learning Platform
CVE Intelligence Hub

CVE-2026-131582: WordPress PagBank / PagSeguro e Vindi para WooCommerce Cross Site Scripting Vulnerability

CVE-2026-131582 explained: high Cross Site Scripting in WordPress PagBank / PagSeguro e Vindi para WooCommerce. CVSS 7.2. Affected versions, detection, fixes and CTE

Last updated: Nov 20, 2026

CVSS
7.2 HIGH
EPSS
n/a
CISA KEV
Not listed
CWE
CWE-79

Sources: National Vulnerability Database, CVE.org, CISA KEV, FIRST EPSS

CVE-2026-131582 Overview

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.

Critical Impact

Remote, unauthenticated attackers can exploit this Cross Site Scripting in WordPress PagBank / PagSeguro e Vindi para WooCommerce. The CVSS base score is 7.2 (High).

Affected Products

  • WordPress PagBank / PagSeguro e Vindi para WooCommerce: see the vendor advisory for the exact affected versions

Discovery Timeline

  • 2026-11-20: CVE-2026-131582 published to the National Vulnerability Database by security@wordfence.com
  • 2026-11-20: last updated in the NVD database

Technical Details for CVE-2026-131582

Vulnerability Analysis

CVE-2026-131582 is a Cross Site Scripting weakness (CWE-79: Cross Site Scripting) in WordPress PagBank / PagSeguro e Vindi para WooCommerce. Based on its CVSS vector, the flaw can be reached over the network, needs no login, and needs no user interaction. Attacker supplied script runs in another user's browser inside the trusted site.

With a CVSS base score of 7.2, apply the vendor fix and confirm exposure on internet facing and business critical assets first.

Root Cause

The weakness is classified as CWE-79: Cross Site Scripting. Attacker supplied script runs in another user's browser inside the trusted site.

Attack Vector

Based on the CVSS vector, the flaw can be reached over the network, needs no login, and needs no user interaction. Attack complexity is low complexity.

No exploitation in the wild is confirmed by CISA at the time of the last update. Check the references below for any vendor or researcher proof of concept.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

Detection Methods for CVE-2026-131582

Detection Strategies

  • Inventory every instance of WordPress PagBank / PagSeguro e Vindi para WooCommerce and compare the running version with the affected range above.
  • Check external attack surface scans for internet facing instances of the component.
  • Run an authenticated vulnerability scan once your scanner ships a check for this CVE.

Monitoring Recommendations

  • Forward WordPress PagBank / PagSeguro e Vindi para WooCommerce application, access and audit logs to your SIEM for retrospective hunting.
  • Alert on new processes, configuration changes or outbound connections from the affected service.
  • Track the vendor advisory and the CISA KEV catalog for changes in exploitation status.

How to Mitigate CVE-2026-131582

Immediate Actions Required

  • Apply the fixed version of WordPress PagBank / PagSeguro e Vindi para WooCommerce named in the vendor advisory.
  • Prioritize internet facing and business critical instances first.
  • Rescan after the change to confirm the exposure is closed.

Patch Information

Use the fixed version listed in the vendor advisory for WordPress PagBank / PagSeguro e Vindi para WooCommerce.

Workarounds

  • If patching must wait, restrict network access to the affected service and place it behind authentication or a web application firewall rule.

CWE References

Technical References

This entry is built directly from NVD, CISA KEV and EPSS data. Verify fixed versions in the vendor advisory before you deploy.

Frequently asked questions

CVE-2026-131582 is a high severity Cross Site Scripting in WordPress PagBank / PagSeguro e Vindi para WooCommerce with a CVSS score of 7.2. Apply the vendor fix and confirm exposure on internet facing and business critical assets first.

Related CVEs

HIGH7.2
CVE-2026-131804
WordPress Seraphinite Accelerator

The Seraphinite Accelerator plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'HTTP_USER_AGENT' parameter in all versions up to, and including, 2.31 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. Exploitation requires that an administrator has previously enabled the 'Enable logging' and 'HTTP trace' diagnostic options in the plugin's Advanced → Debug settings, both of which are disabled by default.

Nov 20, 2026
HIGH7.2
CVE-2026-125094
WordPress Optimole – Optimize Images | Convert WebP & AVIF | CDN & Lazy Load | Image Optimization

The Optimole – Optimize Images | Convert WebP & AVIF | CDN & Lazy Load | Image Optimization plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment' parameter in all versions up to, and including, 4.2.19 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. Exploitation requires the AMP plugin to be active in Transitional or Standard template mode, and comments must be open on the target post, which is the WordPress default.

Nov 20, 2026
HIGH7.2
CVE-2026-96771
WordPress Hydrogen Calendar Embeds

The Hydrogen Calendar Embeds plugin for WordPress is vulnerable to Stored DOM-Based Cross-Site Scripting via ICS Feed Event Fields (SUMMARY/DESCRIPTION/LOCATION) in all versions up to, and including, 3.0.3 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. This requires the attacker to have write access to an ICS feed that has been configured as a calendar source on the target WordPress site.

Nov 20, 2026
HIGH8.1
CVE-2026-126716
WordPress Mega Forms – Drag & Drop Form Builder with Multi-Step & Conditional Logic

The Mega Forms – Drag & Drop Form Builder with Multi-Step & Conditional Logic plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the delete_entry function in all versions up to, and including, 1.7.9 This makes it possible for unauthenticated attackers to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php). The attacker-supplied path is stored via the unauthenticated form submission endpoint, but the actual file deletion only occurs when an administrator subsequently deletes the stored entry — a routine housekeeping action that serves as the detonation trigger. Successful exploitation additionally requires an action by an administrator — the attacker cannot trigger the vulnerability on their own.

Nov 20, 2026
HIGH8.8
CVE-2026-125085
WordPress Nexter Extension – Security, Performance, Code Snippets & Site Toolkit

The Nexter Extension – Security, Performance, Code Snippets & Site Toolkit plugin for WordPress is vulnerable to Privilege Escalation in versions up to, and including, 4.9.0 This is due to the role_switcher_to_view_admin_as() function handling the `reset-view` branch without a capability check or nonce when the caller's own login is supplied, combined with an incomplete cleanup hook (maybe_prevent_switchback_to_administrator) that exits early when the user's current roles equal the stored view role and that is never triggered when WordPress core's WP_User::set_role() short-circuits because the account already has only the target role. This makes it possible for authenticated attackers, with subscriber-level access and above, to elevate their privileges to Administrator.

Nov 20, 2026
HIGH7.5
CVE-2026-125059
WordPress Mang Board

The Mang Board plugin for WordPress is vulnerable to Arbitrary File Deletion via Path Traversal in versions up to, and including, 2.4.8 via the `file_path` column handled by the `mbw_board_files_api_body()` function. The plugin stores an attacker-supplied value directly into the files admin table (no realpath, dot-segment, or directory-containment filtering) and later concatenates it onto `MBW_UPLOAD_PATH` before passing the result to `@unlink()`. This makes it possible for unauthenticated attackers to delete arbitrary files on the affected site's server, including `wp-config.

Nov 20, 2026
All WordPress CVEs in 2026
Your next credential

Earn your free CTEM certification.

Learn to scope, prioritize, validate and mobilize fixes for CVEs like CVE-2026-131582 with a free CTEM certification.

Free to takePublicly verifiable

Beginner / Practitioner / Program Leader

Explore certifications