CVE-2023-48286

Accept Stripe Payments <= 2.0.79 - Insecure Direct Object Reference

2023-11-23 00:00
Joshua Chan

Strategic Overview

Status
Patched in 2.0.80
Affected Plugin
Accept Stripe Payments
Affected Version
<= 2.0.79
CVSS
5.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2023-48286
View all Accept Stripe Payments vulnerabilities

At a glance

CVE-2023-48286 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Accept Stripe Payments WordPress plugin, affecting versions <= 2.0.79. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.0.80; sites on affected versions should update now. Disclosed November 2023, reported by Joshua Chan.

Vulnerability Overview

The Stripe Payments plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the handle_create_pi() function in versions up to, and including, 2.0.79. This makes it possible for unauthenticated attackers to purchase products in another currency which may result in attackers paying lower amouns than they should be.

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, and no interaction from a victim user.

CWE-639: Authorization Bypass Through User-Controlled Key

Accept Stripe Payments <= 2.0.79 carries this weakness at handle_create_pi(), and reaching it takes a caller who can reach the endpoint. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.

Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For Accept Stripe Payments the fix is 2.0.80: builds <= 2.0.79 are affected, anything from 2.0.80 onward is not.

Remediation

Update to version 2.0.80, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Accept Stripe Payments 2.0.80 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2023-48286https://www.wordfence.com/threat-intel/vulnerabilities/id/44d14692-d90a-45f9-afb4-0666ce4b3397https://nvd.nist.gov/vuln/detail/CVE-2023-48286

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C