Radar sectionsDatabase
Check my site
WordPress plugin

Payment Plugins for Stripe WooCommerce <= 4.0.17 — Reflected DOM-Based Cross-Site Scripting via '#response' URL Fragment

CVE-2026-89100Published · Updated

Action summary

Affected: ≤4.0.17Update to 4.0.18 or newer

All remediation steps
Severity
Medium6.1
CVSS
6.1
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
What does this vector mean?
AV:N Attack vector
Network
AC:L Attack complexity
Low
PR:N Privileges required
None
UI:R User interaction
Required
S:C Scope
Changed
C:L Confidentiality
Low
I:L Integrity
Low
A:N Availability
None
Weakness
CWE-79 Cross-Site Scripting
Required access
No account needed
Exploit prediction (EPSS)
0.2% chance in 30 days12th percentile
CISA KEV
Not listed

Am I affected?

Payment Plugins for Stripe WooCommerce woo-stripe-payment

  1. Affected≤ 4.0.17
  2. Patched in4.0.18

Update to 4.0.18 or newer.

You are affected if you run ≤ 4.0.17. Version 4.0.18 and later are not affected by this issue.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under Payment Plugins for Stripe WooCommerce.
  • No admin access? Run a passive check of your site. It reads public files only.
  • No account is needed to exploit this. Treat any exposed site on an affected version as at risk.

What to do

  1. Update to version 4.0.18, or a newer patched version
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch Payment Plugins for Stripe WooCommerce to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to Adrien Brunner.

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.

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

More in Payment Plugins for Stripe WooCommerce

All 4
More vulnerabilities in Payment Plugins for Stripe WooCommerce
SeverityVulnerabilityCVEPublished
Medium5.3Unauthenticated Information Exposure
≤4.0.11Update to 4.0.12
CVE-2026-80339
Medium5.3Missing Authorization to Unauthenticated Arbitrary Order Status Modification via Empty Webhook Secret
≤4.0.7Update to 4.0.8
CVE-2026-12654
Medium5.3Missing Authorization
≤4.0.7Update to 4.0.8
CVE-2026-59530

Same weakness (Cross-Site Scripting)

All Cross-Site Scripting
Other Cross-Site Scripting vulnerabilities
SeverityVulnerabilityCVEPublished
High7.2Unauthenticated Stored Cross-Site Scripting via Comment User-Agent HeaderCVE-2026-120688
Critical9.8Unauthenticated Arbitrary File Upload via File Upload via Public Form SubmissionCVE-2026-125055
Critical9.8Unauthenticated PHP Object Injection to Remote Code Execution via 'form' ParameterCVE-2026-119077
Medium5.3Unauthenticated Sensitive Information Exposure in 'search' Parameter
Customer Reviews for WooCommerce≤5.127.0Update to 5.128.0
CVE-2026-121518

Timeline

  1. CVE published

    Severity medium, CVSS 6.1

  2. Record last updated

Sources & licenses

Wordfence record
Vulnerability data
Wordfence Intelligence. Copyright 2012-2026 Defiant Inc. Licensed under the CC BY-SA 4.0.
CVE® identifiers
Copyright 1999-2026 The MITRE Corporation. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
EPSS
Exploit Prediction Scoring System by FIRST.org.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Are you sure?