VulnCrest
Search
Create account
Report an incident
Radar sectionsDatabase
Check my site
WordPress plugin

WooCommerce Payments <= 5.9.0 — Missing Authorization via redirect_pay_for_order_to_update_payment_method

CVE-2023-35916Published · Updated

Action summary

Affected: ≤5.9.0Update to 5.9.1 or newer

All remediation steps
Watch plugin
Severity
Medium6.5
CVSS
6.5
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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:N User interaction
None
S:U Scope
Unchanged
C:L Confidentiality
Low
I:L Integrity
Low
A:N Availability
None
Weakness
CWE-639 Authorization Bypass Through User-Controlled Key
Required access
No account needed
Exploit prediction (EPSS)
No score
CISA KEV
Not listed
On this page8

Am I affected?

WooPayments: Integrated WooCommerce Payments woocommerce-payments

  1. Affected≤ 5.9.0
  2. Patched in5.9.1

Update to 5.9.1 or newer.

You are affected if you run ≤ 5.9.0. Version 5.9.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 version 5.9.1, or a newer patched version
  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, credited to Rafie Muhammad.

The WooCommerce Payments plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the redirect_pay_for_order_to_update_payment_method function in versions up to, and including, 5.9.0. This makes it possible for unauthenticated attackers to change payment information for other users' orders.

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
Critical9.85.6.1 Authentication Bypass and Privilege Escalation
4.8.0 – 5.6.1Update to 5.6.2
CVE-2023-28121

Timeline

  1. CVE published

    Severity medium, CVSS 6.5

  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.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Jump to

Are you sure?