Accept Stripe Payments <= 2.0.63 - Authenticated Stored Cross-Site Scripting
Strategic Overview
- Status
- Patched in 2.0.64
- Affected Plugin
- Accept Stripe Payments
- Affected Version
<= 2.0.63- CVSS
- 5.5Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2022-2194
At a glance
CVE-2022-2194 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Accept Stripe Payments WordPress plugin, affecting versions <= 2.0.63. It carries a CVSS score of 5.5 (reachable over the network; low attack complexity). Exploitation requires an authenticated account. The issue is fixed in version 2.0.64; sites on affected versions should update now. Disclosed June 2022, reported by iohex.
Vulnerability Overview
The Accept Stripe Payments WordPress plugin before 2.0.64 does not sanitize and escape some of its settings, allowing high privilege users such as admin to perform cross-Site Scripting attacks even when the unfiltered_html capability is disallowed.
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 interaction from a victim user.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Reaching this weakness in Accept Stripe Payments <= 2.0.63 takes any authenticated account. 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 Accept Stripe Payments the fix is 2.0.64: builds <= 2.0.63 are affected, anything from 2.0.64 onward is not.
Remediation
Update to version 2.0.64, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Accept Stripe Payments: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Accept Stripe Payments 2.0.64 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Accept Stripe Payments
- 6.1CVE-2026-81423: Accept Stripe Payments < 2.1.4 Open Redirect
CVE-2026-81423 - 5.3CVE-2026-81424: Accept Stripe Payments < 2.1.4 IDOR
CVE-2026-81424 - 5.3CVE-2026-42752: Accept Stripe Payments <= 2.0.98 Payment Bypass
CVE-2026-42752 - 5.3CVE-2023-48285: Accept Stripe Payments <= 2.0.79 Content Injection
CVE-2023-48285 - 5.3CVE-2023-48286: Accept Stripe Payments <= 2.0.79 IDOR
CVE-2023-48286
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C