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

WooCommerce Stripe Payment Gateway <= 7.6.1 — Insecure Direct Object Reference via update_payment_intent_ajax

CVE-2023-51502Published · Updated

Action summary

Affected: ≤7.6.1Update to 7.6.2 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?

WooCommerce Stripe Payment Gateway woocommerce-gateway-stripe

  1. Affected≤ 7.6.1
  2. Patched in7.6.2

Update to 7.6.2 or newer.

You are affected if you run ≤ 7.6.1. Version 7.6.2 and later are not affected by this issue.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under WooCommerce Stripe Payment Gateway.
  • 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 7.6.2, or a newer patched version
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch WooCommerce Stripe Payment Gateway to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to Rafie Muhammad.

The WooCommerce Stripe Payment Gateway plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 7.6.1 via the update_payment_intent_ajax due to missing validation on a user controlled key. This makes it possible for unauthenticated attackers to make updates to payments that don't belong to their orders.

Exploits & references

Proof-of-concept & detection

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

Advisories & patches

More in WooCommerce Stripe Payment Gateway

All 6
More vulnerabilities in WooCommerce Stripe Payment Gateway
SeverityVulnerabilityCVEPublished
Medium4.311.0.1 - Insecure Storage of Password
10.9.0 – 11.0.1Update to 11.1.0
CVE-2026-123145
Medium6.5Missing Authorization to Unauthenticated Order Status Manipulation via 'order' Parameter
≤10.7.0Update to 10.8.0
CVE-2026-2381
Medium5.4Cross-Site Request Forgery
<7.6.1Update to 7.6.1
CVE-2023-44999
Medium6.3Missing Authorization
≤7.4.0Update to 7.4.1
CVE-2023-35049
High7.5Unauthenticated Insecure Direct Object Reference to Sensitive Information Disclosure
≤7.4.0Update to 5.5.1 or 5.6.3 or 5.7.1 or 5.8.2 or 5.9.1 or 6.0.1 or 6.1.1 or 6.2.1 or 6.3.1 or 6.4.4 or 6.5.2 or 6.6.1 or 6.7.1 or 6.8.1 or 6.9.1 or 7.0.3 or 7.1.1 or 7.2.1 or 7.3.1 or 7.4.1
CVE-2023-34000

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?