HomeWordPress vulnerabilitiesAccept Stripe Payments
Accept Stripe Payments vulnerabilities
Accept Stripe Payments has 5 known vulnerabilities in this database. The most recent published record is dated 5 Sep 2026.
- Known vulnerabilities
- 5
- Active installs
- 20,000+
- Latest version
- 2.1.4
- Last updated
- 2 Sep 2026
- Most recent
- 5 Sep 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Open redirect CVE-2026-81423 | Medium 4.3 | Before 2.1.4 | Fixed in 2.1.4 | 5 Sep 2026 |
| Broken access control CVE-2026-81424 | Medium 5.3 | Before 2.1.4 | Fixed in 2.1.4 | 5 Sep 2026 |
| Cross-site scripting (XSS) CVE-2021-47983 | Medium 6.4 | Before 2.0.40 | Fixed in 2.0.40 | 8 Jun 2026 |
| Cross-site scripting (XSS) CVE-2024-7353 | Medium 5.4 | Up to 2.0.86 | Fixed in a later version (latest 2.1.4) | 7 Aug 2024 |
| Cross-site scripting (XSS) CVE-2022-2194 | Medium 4.8 | Before 2.0.64 | Fixed in 2.0.64 | 17 Jul 2022 |
Read the published descriptions
- CVE-2026-81423, 5 Sep 2026
- The Accept Stripe Payments WordPress plugin before 2.1.4 does not validate a user-supplied URL before using it in a redirect, allowing unauthenticated attackers to redirect visitors to an arbitrary external website, which can be leveraged for phishing. CVE record
- CVE-2026-81424, 5 Sep 2026
- The Accept Stripe Payments WordPress plugin before 2.1.4 does not verify that the product fulfilled when a checkout is completed matches the product the authoritative payment was actually made for, checking only that the amount paid is at least the referenced product's price, allowing unauthenticated attackers who complete a genuine payment to obtain fulfilment for a different, equal- or lower-priced product than the one they paid for. CVE record
- CVE-2021-47983, 8 Jun 2026
- WordPress Plugin Stripe Payments before 2.0.40 contains a stored cross-site scripting vulnerability that allows authenticated attackers to inject malicious scripts through the AcceptStripePayments-settings[currency_code] parameter. Attackers can submit POST requests to /wp-admin/options.php with script payloads in the currency_code field to execute arbitrary JavaScript in administrator browsers when settings are viewed. CVE record
- CVE-2024-7353, 7 Aug 2024
- The Accept Stripe Payments plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's accept_stripe_payment_ng shortcode in all versions up to, and including, 2.0.86 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
- CVE-2022-2194, 17 Jul 2022
- 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. CVE record
What to do if you run Accept Stripe Payments
If you run Accept Stripe Payments, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Accept Stripe Payments vulnerabilities
Free. We email you when a new vulnerability is published for Accept Stripe Payments, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.