CVE-2026-81423

Accept Stripe Payments < 2.1.4 - Unauthenticated Open Redirect

2026-09-03 00:00

Strategic Overview

Status: Patched in 2.1.4
Affected Plugin: Accept Stripe Payments
Affected Version: < 2.1.4
CVSS: 6.1Medium
Weakness type: CWE-601 · URL Redirection to Untrusted Site ('Open Redirect')
CVE: CVE-2026-81423

View all Accept Stripe Payments vulnerabilities

At a glance

CVE-2026-81423 is a medium-severity URL Redirection to Untrusted Site ('Open Redirect') vulnerability in the Accept Stripe Payments WordPress plugin, affecting versions < 2.1.4. 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 2.1.4; sites on affected versions should update now. Disclosed September 2026, reported by Usama Arshad.

Vulnerability Overview

The Accept Stripe Payments plugin for WordPress is vulnerable to Open Redirect in all versions up to 2.1.4 (exclusive). This is due to insufficient validation on the redirect url supplied. This makes it possible for unauthenticated attackers to redirect users to potentially malicious sites if they can successfully trick them into performing an action.

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-601: URL Redirection to Untrusted Site ('Open Redirect')

Reaching this weakness in Accept Stripe Payments < 2.1.4 takes no account at all. An open redirect is a page that takes a destination from the request and sends the browser there without checking that the destination belongs to the site.

A link that starts on a trusted domain finishes on an attacker's, which is what makes phishing and consent-screen abuse credible to the person clicking it. For Accept Stripe Payments the fix is 2.1.4: builds < 2.1.4 are affected, anything from 2.1.4 onward is not.

Remediation

Update to version 2.1.4, or a newer patched version

How does WordSec protect against this?

Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Accept Stripe Payments 2.1.4 closes this, and updating the plugin is the step that ends it.

Firewall
Login Security
Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-81423 https://www.wordfence.com/threat-intel/vulnerabilities/id/3133be9d-13d4-4fb4-bbcf-88a68cca1933 https://nvd.nist.gov/vuln/detail/CVE-2026-81423

Related records

Other vulnerabilities in Accept Stripe Payments

CVSS Vector

6.1

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionRequired
ScopeChanged
ConfidentialityLow
IntegrityLow
AvailabilityNone

This record contains material that is subject to copyright

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

https://www.cve.org/Legal/TermsOfUse

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/