CVE-2026-19073

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreHIGH confidence

Score 5.3 from GitHub Security Advisory published 2026-08-12. 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 Order Sync with Zendesk for WooCommerce WordPress plugin before 2.2.3 does not perform any capability check on one of its REST API endpoints, and does not verify that the requester owns the account being queried, allowing unauthenticated attackers to retrieve the order history and purchase totals of any customer whose email address they know or can enumerate.

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
11%
KEV
Not listed

Published

August 12, 2026

Last Modified

August 12, 2026

Advisory Details (1)

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

Order Sync with Zendesk for WooCommerce < 2.2.3 – Unauthenticated Customer Order Data Disclosure | CVE 2026-19073 | Plugin Vulnerabilities

https://wpscan.com/vulnerability/8c8ca8ff-e0e8-4e9c-b79b-7f95816a9113/

Vendor Advisories for CVE-2026-19073(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-20 22:55 UTCEPSS rescore
  2. 2026-08-20 22:23 UTCGHSA enrichment
  3. 2026-08-19 21:24 UTCEG score recompute
  4. 2026-08-19 21:24 UTCGHSA enrichment
  5. 2026-08-19 17:03 UTCEPSS rescore
  6. 2026-08-18 20:16 UTCEG score recompute
  7. 2026-08-18 20:15 UTCGHSA enrichment
  8. 2026-08-18 13:48 UTCEPSS rescore
  9. 2026-08-17 19:15 UTCEG score recompute
  10. 2026-08-17 19:15 UTCGHSA enrichment
  11. 2026-08-17 13:47 UTCEPSS rescore
  12. 2026-08-16 17:38 UTCEG score recompute
  13. 2026-08-16 17:38 UTCGHSA enrichment
  14. 2026-08-16 14:56 UTCEPSS rescore
  15. 2026-08-16 02:14 UTCEPSS rescore
  16. 2026-08-15 16:35 UTCEG score recompute
  17. 2026-08-15 16:35 UTCGHSA enrichment
  18. 2026-08-15 01:30 UTCEPSS rescore
  19. 2026-08-14 15:35 UTCEG score recompute
  20. 2026-08-14 15:35 UTCGHSA enrichment
  21. 2026-08-13 22:00 UTCEPSS rescore
  22. 2026-08-13 14:36 UTCEG score recompute
  23. 2026-08-13 14:36 UTCGHSA enrichment
  24. 2026-08-12 13:50 UTCEPSS rescore
  25. 2026-08-12 13:37 UTCGHSA enrichment
Show 7 more
  1. 2026-08-12 12:35 UTCEG score recompute 5.30
  2. 2026-08-12 12:35 UTCGHSA enrichment
  3. 2026-08-12 12:34 UTCMITRE cvelistV5CVSS v3 → 5.3 · severity → MEDIUM
  4. 2026-08-12 06:31 UTCGHSA enrichment
  5. 2026-08-12 06:30 UTCNVD update
  6. 2026-08-12 06:06 UTCEG score recompute
  7. 2026-08-12 06:03 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-19073?
CVE-2026-19073 is a medium vulnerability published on August 12, 2026. The Order Sync with Zendesk for WooCommerce WordPress plugin before 2.2.3 does not perform any capability check on one of its REST API endpoints, and does not verify that the requester owns the account being queried, allowing unauthenticated attackers to retrieve the order history and purchase…
When was CVE-2026-19073 disclosed?
CVE-2026-19073 was first published in the National Vulnerability Database on August 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-19073 actively exploited?
CVE-2026-19073 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 89.0% of all scored CVEs.
What is the CVSS score of CVE-2026-19073?
CVE-2026-19073 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-19073?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-19073, 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-19073

Explore →

Is Your Infrastructure Affected by CVE-2026-19073?

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