# Accept Stripe Payments <= 2.1.4 - Unauthenticated Stored Cross-Site Scripting via Order Event Comments

- **ID:** WPSEC-2026-3624
- **Plugin:** Accept Stripe Payments (`stripe-payments`), https://wordpress.org/plugins/stripe-payments/
- **Affected versions:** all versions before 2.1.5
- **Fixed in:** 2.1.5 (Update to 2.1.5 or later.)
- **Severity:** High 7.2 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N)
- **Weakness:** CWE-79
- **Usage among sites WPSec scans:** plugin Medium, affected versions Medium (as of 2026-11-21)
- **Attack surface analysis:** https://attacksurface.wpsec.com/plugin/stripe-payments
- **Fix released:** 2026-11-20
- **Published:** 2026-11-21
- **URL:** https://wpsec.com/vuln/WPSEC-2026-3624/

## Description

The Accept Stripe Payments plugin for WordPress is vulnerable to Stored Cross-Site Scripting via order event comments in all versions up to, and including, 2.1.4, due to insufficient input sanitization and output escaping. The publicly accessible asp_pp_confirm_pi AJAX action forwards visitor-supplied confirm options to Stripe and stores the resulting Stripe API error message, which can echo those values, as an order event comment. The comment is then printed without escaping in the order events meta box and the order list status tooltip. This makes it possible for unauthenticated attackers to inject arbitrary web scripts that execute whenever an administrator views the affected order or the orders list.

## References

- https://wpsec.com/vuln/WPSEC-2026-3624/
- https://plugins.svn.wordpress.org/stripe-payments/tags/2.1.5/
- https://wordpress.org/plugins/stripe-payments/

Source: WPSec, https://wpsec.com/vuln/WPSEC-2026-3624/

License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Free to use, share and adapt, also commercially, if you credit WPSec and link to this advisory.
