Blog

"Prevention is cheaper than a breach"

Home / Threats / CVE-2026-17012

CVE-2026-17012 - Stripe With Subscriptions For Woocommerce Plugin

CVE-2026-17012

The Accept PayPal & Stripe with Subscriptions for WooCommerce WordPress plugin through 3.1.0 does not verify that the PayPal account which received a payment matches the merchant's configured account before marking the order as paid, allowing unauthenticated buyers to complete a WooCommerce order by paying the full amount to their own PayPal account instead of the merchant's.

CVE-2026-17012

UNKNOWN CVSS 0.0 Published 2026-08-10 Updated 2026-08-10
AI Risk Low (14/100) Active Exploit: No strong signal Published Exploit: No public exploit references Priority: P5 Monitor
Severity Band UNKNOWN
CVSS Vector Unspecified
Affected Components 2
Reference Links 1
AI Risk Engine Low (14/100)
Exploitability High
Active Exploitation No strong signal
Published Exploit Status No public exploit references

Threat Timeline

  1. 2026-08-10 CVE published and first recorded in the threat feed.
  2. 2026-08-10 Record updated with latest vulnerability metadata.
  3. 2026-08-11 AI technical context refreshed for mitigation and impact guidance.
  4. Now Monitoring for follow-up changes, linked references, and new related CVEs.

AI Context

Machine-generated threat intelligence

AI Updated 18 hours ago

AI enriched 18 hours ago (2026-08-11 18:38 UTC)

Technical Summary

The Accept PayPal & Stripe with Subscriptions for WooCommerce WordPress plugin through 3.1.0 does not verify that the PayPal account which received a payment matches the merchant's configured account before marking the order as paid, allowing unauthenticated buyers to complete a WooCommerce order by paying the full amount to their own PayPal account instead of the merchant's.

Potential Impact

Severity is UNKNOWN (CVSS 0.0). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.

Exploitability Assessment

Exploitability is assessed as High based on remote code execution potential, low-bar exploit prerequisites.

Primary risk drivers: remote code execution potential, low-bar exploit prerequisites

Mitigation Recommendations

Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.

Detection & Monitoring

Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.

Business Impact Lens

AI risk score 14/100 (Low, High) with priority P5 Monitor. Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.

Scroll to top