Description
The Accept Stripe Payments WordPress plugin before 2.1.4 does not verify that the product fulfilled when a checkout is completed matches the product the authoritative payment was actually made for, checking only that the amount paid is at least the referenced product's price, allowing unauthenticated attackers who complete a genuine payment to obtain fulfilment for a different, equal- or lower-priced product than the one they paid for.
Published: 2026-09-05
Score: n/a
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The Accept Stripe Payments WordPress plugin before version 2.1.4 fails to verify that the product being fulfilled exactly matches the product for which a payment was actually made. Instead, it only checks that the amount paid is at least the price of the referenced product. This flaw allows an attacker who has completed a legitimate payment to obtain fulfillment for a different product of equal or lower price, effectively stealing goods without additional payment.

Affected Systems

Any WordPress site running the Accept Stripe Payments plugin with a version earlier than 2.1.4 is affected. The plugin is a commercial WordPress add‑on, but the vendor name is listed as Unknown:Accept Stripe Payments in the CNA data. No user authentication is required to trigger the issue; the production environment simply lacks a check that the fulfillment request references the same product as the payment confirmation.

Risk and Exploitability

The lack of a public CVSS score or EPSS value makes the formal severity unclear, but the vulnerability can directly lead to financial loss and inventory misallocation. Because an attacker only needs to complete a genuine payment, the exploit requires no additional account access. The vulnerability is not listed in the CISA KEV catalog. The core weakness is an Insecure Direct Object Reference (IDOR) that permits unauthenticated substitution of protected resources. The risk of exploitation is significant if sites continue to run the affected plugin without applying the recommended patch.

Generated by OpenCVE AI on September 5, 2026 at 08:22 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade the Accept Stripe Payments plugin to version 2.1.4 or later
  • If an immediate upgrade is not possible, temporarily block or disable the fulfillment API until the plugin can be patched or the feature re‑implemented with proper validation
  • Modify the server‑side logic to compare the product identifier from the payment confirmation with the fulfillment request, rejecting any mismatches before processing

Generated by OpenCVE AI on September 5, 2026 at 08:22 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sat, 05 Sep 2026 08:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-639

Sat, 05 Sep 2026 06:30:00 +0000

Type Values Removed Values Added
Description The Accept Stripe Payments WordPress plugin before 2.1.4 does not verify that the product fulfilled when a checkout is completed matches the product the authoritative payment was actually made for, checking only that the amount paid is at least the referenced product's price, allowing unauthenticated attackers who complete a genuine payment to obtain fulfilment for a different, equal- or lower-priced product than the one they paid for.
Title Accept Stripe Payments < 2.1.4 - Unauthenticated Product Substitution via IDOR
References

Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: WPScan

Published:

Updated: 2026-09-05T06:00:06.632Z

Reserved: 2026-08-26T19:08:06.347Z

Link: CVE-2026-81424

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-09-05T07:17:12.997

Modified: 2026-09-05T07:17:12.997

Link: CVE-2026-81424

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-05T08:30:06Z

Weaknesses
  • CWE-639

    Authorization Bypass Through User-Controlled Key