CVE-2026-17012

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreHIGH confidence

Score 5.3 from GitHub Security Advisory published 2026-08-10. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this week
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
5.3
EG Score
5.3(high)
EG Risk
39(Track)
EG Risk 39/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity53% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
12%
KEV
Not listed

Published

August 10, 2026

Last Modified

August 11, 2026

Advisory Details (1)

Auto-updated Aug 11, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

Restore PayPal Standard for WooCommerce <= 3.1.0 – Payment Bypass via Unvalidated receiver_email | CVE 2026-17012 | Plugin Vulnerabilities

https://wpscan.com/vulnerability/01cc2578-8bf8-4889-9e21-7b78cae074d7/

Vendor Advisories for CVE-2026-17012(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 20× in last 7d / 32× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-19 18:45 UTCEG score recompute
  2. 2026-08-19 18:45 UTCGHSA enrichment
  3. 2026-08-19 17:03 UTCEPSS rescore
  4. 2026-08-18 17:25 UTCEG score recompute
  5. 2026-08-18 17:25 UTCGHSA enrichment
  6. 2026-08-18 13:48 UTCEPSS rescore
  7. 2026-08-17 17:32 UTCEG score recompute
  8. 2026-08-17 17:32 UTCGHSA enrichment
  9. 2026-08-17 13:47 UTCEPSS rescore
  10. 2026-08-16 18:10 UTCEG score recompute
  11. 2026-08-16 18:10 UTCGHSA enrichment
  12. 2026-08-16 14:56 UTCEPSS rescore
  13. 2026-08-16 02:14 UTCEPSS rescore
  14. 2026-08-15 18:48 UTCEG score recompute
  15. 2026-08-15 18:48 UTCGHSA enrichment
  16. 2026-08-15 01:30 UTCEPSS rescore
  17. 2026-08-14 19:25 UTCEG score recompute
  18. 2026-08-14 19:25 UTCGHSA enrichment
  19. 2026-08-13 22:00 UTCEPSS rescore
  20. 2026-08-13 20:03 UTCGHSA enrichment
  21. 2026-08-12 20:41 UTCEG score recompute
  22. 2026-08-12 20:41 UTCGHSA enrichment
  23. 2026-08-12 13:50 UTCEPSS rescore
  24. 2026-08-11 21:19 UTCGHSA enrichment
  25. 2026-08-11 20:30 UTCEG score recompute▲ 5.30
Show 7 more
  1. 2026-08-11 20:30 UTCGHSA enrichment
  2. 2026-08-11 20:30 UTCMITRE cvelistV5CVSS v3 → 5.3 · severity → MEDIUM
  3. 2026-08-11 13:42 UTCEPSS rescore
  4. 2026-08-11 00:00 UTCEPSS rescore
  5. 2026-08-10 07:19 UTCNVD update
  6. 2026-08-10 06:41 UTCEG score recompute
  7. 2026-08-10 06:41 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-17012?
CVE-2026-17012 is a medium vulnerability published on August 10, 2026. 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…
When was CVE-2026-17012 disclosed?
CVE-2026-17012 was first published in the National Vulnerability Database on August 10, 2026, with the most recent update on August 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-17012 actively exploited?
CVE-2026-17012 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 87.9% of all scored CVEs.
What is the CVSS score of CVE-2026-17012?
CVE-2026-17012 has a CVSS v3.1 base score of 5.3 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-17012?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-17012, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-17012

Explore →

Is Your Infrastructure Affected by CVE-2026-17012?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs