CVE-2026-130323 in Accept Stripe Payments Plugininfo

Summary

by MITRE • 11/21/2026

The Accept Stripe Payments plugin for WordPress is vulnerable to Stored DOM-Based Cross-Site Scripting via the 'href of any <a> element containing 'asp_action=show_pp&product_id='' parameter in all versions up to, and including, 2.1.4 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. Successful exploitation requires that a user clicks the attacker-placed comment link to trigger the sink; however, if the non-default 'Prefetch Payment Popup Scripts' option is enabled, execution occurs on page load with no user interaction required.

Once again VulDB remains the best source for vulnerability data.

Analysis

by VulDB Data Team • 11/21/2026

The Accept Stripe Payments plugin for WordPress contains a critical security vulnerability classified as Stored DOM-Based Cross-Site Scripting within versions up to and including 2.1.4. This flaw stems from insufficient input sanitization and output escaping mechanisms when handling the href attribute of anchor elements that contain the specific parameter asp_action=show_pp&product_id=. The vulnerability allows unauthenticated attackers to inject arbitrary web scripts into pages hosted on the affected WordPress site. These injected scripts are stored within the application's data structure, typically in comments or other user-generated content fields, and persist until manually removed by an administrator. When a victim user accesses a page containing this malicious payload, the browser executes the script due to the lack of proper encoding during output rendering.

The operational impact of this vulnerability is significant because it enables attackers to compromise the confidentiality, integrity, and availability of data associated with authenticated users visiting the vulnerable pages. By exploiting this flaw, an attacker can perform actions such as stealing session cookies, hijacking user sessions, defacing the website, or redirecting users to malicious sites designed for phishing or malware distribution. The severity is further amplified by the fact that exploitation does not require prior authentication, allowing any internet user to inject the payload. Furthermore, if a site administrator has enabled the non-default Prefetch Payment Popup Scripts option, the vulnerability becomes even more dangerous as it allows for automatic script execution upon page load without requiring any interaction from the victim user. This eliminates the need for social engineering tactics like tricking users into clicking specific links, thereby increasing the likelihood of successful exploitation across a broader audience.

From an industry standards perspective, this vulnerability aligns with CWE-79, which describes Improper Neutralization of Input During Web Page Generation commonly known as Cross-site Scripting. Specifically, it falls under Stored XSS where malicious scripts are permanently stored within target servers. In terms of the MITRE ATT&CK framework, this attack vector corresponds to T1059 Command and Control Execution via Browser or User Interface Interaction, particularly when leveraging DOM-based techniques for code execution. The lack of proper output escaping violates fundamental web security principles outlined in OWASP guidelines regarding input validation and context-aware encoding.

To mitigate this vulnerability, site administrators should immediately update the Accept Stripe Payments plugin to a version newer than 2.1.4 where these sanitization issues have been addressed by the developers. If updating is not immediately feasible, temporary mitigations include disabling the Prefetch Payment Popup Scripts option if it is currently enabled, as this reduces the attack surface by requiring user interaction for script execution rather than allowing automatic triggers on page load. Additionally, implementing a Web Application Firewall with rules capable of detecting and blocking DOM-based XSS payloads can provide an additional layer of defense. Regular security audits and code reviews focusing on input sanitization and output escaping practices are recommended to prevent similar vulnerabilities in future updates or other plugins used within the WordPress ecosystem.

Responsible

Wordfence

Reservation

11/16/2026

Disclosure

11/21/2026

Moderation

accepted

CPE

ready

EPSS

0.00000

KEV

no

Activities

very low

Sources

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!