Radar sectionsDatabase
Check my site
WordPress plugin

WooCommerce Payments <= 4.5.0 — Payment Bypass

9d604200-91b0-4885-8fe2-1323b9d6fed5Published · Updated

Action summary

Affected: ≤4.5.0Update to 3.9.4 or 4.0.3 or 4.1.1 or 4.2.2 or 4.3.1 or 4.4.1 or 4.5.1 or newer

Fixed versions are per release branch: update to the fix for the branch you run.

All remediation steps
Severity
Medium5.3
CVSS
5.3
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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:N User interaction
None
S:U Scope
Unchanged
C:N Confidentiality
None
I:L Integrity
Low
A:N Availability
None
Weakness
CWE-233 Improper Handling of Parameters
Required access
No account needed
Exploit prediction (EPSS)
No score
CISA KEV
Not listed

Am I affected?

WooPayments: Integrated WooCommerce Payments woocommerce-payments

  1. Affected≤ 4.5.0
  2. Patched in3.9.4 / 4.0.3 / 4.1.1 / 4.2.2 / 4.3.1 / 4.4.1 / 4.5.1

Update to 3.9.4 / 4.0.3 / 4.1.1 / 4.2.2 / 4.3.1 / 4.4.1 / 4.5.1 or newer.

You are affected if you run ≤ 4.5.0. Version 3.9.4, 4.0.3, 4.1.1, 4.2.2, 4.3.1, 4.4.1, 4.5.1 and later are not affected by this issue.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under WooPayments: Integrated WooCommerce Payments.
  • 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 one of the following versions, or a newer patched version: 3.9.4, 4.0.3, 4.1.1, 4.2.2, 4.3.1, 4.4.1, 4.5.1
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch WooPayments: Integrated WooCommerce Payments to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence.

The WooCommerce Payments plugin for WordPress is vulnerable to payment bypass in versions up to, and including, 4.5.0. This is due to insufficient controls on checkout payment intent. This makes it possible for unauthenticated users to complete purchases without paying for them.

Exploits & references

Proof-of-concept & detection

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

Advisories & patches

More in WooPayments: Integrated WooCommerce Payments

All 7
More vulnerabilities in WooPayments: Integrated WooCommerce Payments
SeverityVulnerabilityCVEPublished
Medium6.5Missing Authorization to Unauthenticated Plugin Settings Update via save_upe_appearance_ajax
≤10.5.1Update to 10.6.0
CVE-2026-1710
Medium5.3Unauthenticated Insecure Direct Object Reference
≤6.6.2Update to 6.7.0
CVE-2023-51503
Medium6.4Authenticated (Contributor+) Stored Cross-Site Scripting
≤6.4.2Update to 6.5.0
CVE-2023-49828
Medium6.6Authenticated (Shop manager+) SQL Injection via currency parameters
≤5.9.0Update to 5.9.1
CVE-2023-35915
Medium6.5Missing Authorization via redirect_pay_for_order_to_update_payment_method
≤5.9.0Update to 5.9.1
CVE-2023-35916

Timeline

  1. CVE published

    Severity medium, CVSS 5.3

  2. Record last updated

Sources & licenses

Vulnerability data
Wordfence Intelligence. Copyright 2012-2026 Defiant Inc. Licensed under the CC BY-SA 4.0.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Are you sure?