Payment Plugins for Stripe WooCommerce <= 4.0.17 - Reflected DOM-Based Cross-Site Scripting via '#response' URL Fragment
Strategic Overview
- Status
- Patched in 4.0.18
- Affected Plugin
- Payment Plugins for Stripe WooCommerce
- Affected Version
<= 4.0.17- CVSS
- 6.1Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2026-89100
At a glance
CVE-2026-89100 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Payment Plugins for Stripe WooCommerce WordPress plugin, affecting versions <= 4.0.17. It carries a CVSS score of 6.1 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 4.0.18; sites on affected versions should update now. Disclosed October 2026, reported by Adrien Brunner.
Vulnerability Overview
The Payment Plugins for Stripe WooCommerce plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via '#response' URL Fragment in all versions up to, and including, 4.0.17 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 the 'Generic Errors' setting is unchecked, causing getErrorMessage() to return the raw Stripe error string unchanged rather than substituting a mapped safe message.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Payment Plugins for Stripe WooCommerce <= 4.0.17 carries this weakness at getErrorMessage(), and reaching it takes a caller who can reach the endpoint. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.
Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For Payment Plugins for Stripe WooCommerce the fix is 4.0.18: builds <= 4.0.17 are affected, anything from 4.0.18 onward is not.
Remediation
Update to version 4.0.18, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Payment Plugins for Stripe WooCommerce: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Payment Plugins for Stripe WooCommerce 4.0.18 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in Payment Plugins for Stripe WooCommerce
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C