CVE-2026-10599

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-07. a secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: Elevated riskExposed: 0

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

The Integrate PhonePe with WooCommerce WordPress plugin through 1.2.1 does not validate that a verified payment transaction belongs to the order being marked as paid, nor does it verify the authenticity of its payment-completion request, allowing unauthenticated attackers to reuse a single valid transaction to mark arbitrary orders as paid and bypass payment.

CVSS v3
7.5
EG Score
7.5(high)
EG Risk
65(Attend)
EG Risk 65/100SSVC: Attend

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
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

August 6, 2026

Last Modified

August 7, 2026

Advisory Details (1)

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

Integrate PhonePe with WooCommerce <= 1.2.1 – Unauthenticated Payment Bypass via Transaction ID Reuse | CVE 2026-10599 | Plugin Vulnerabilities

https://wpscan.com/vulnerability/a1aae05d-63d0-4cde-8a9c-996f58f58e48/

Vendor Advisories for CVE-2026-10599(1)

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 28× in last 7d / 60× 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 07:30 UTCGHSA enrichment
  2. 2026-08-19 20:37 UTCEG score recompute
  3. 2026-08-19 20:37 UTCGHSA enrichment
  4. 2026-08-19 17:03 UTCEPSS rescore
  5. 2026-08-19 09:43 UTCGHSA enrichment
  6. 2026-08-18 22:49 UTCEG score recompute
  7. 2026-08-18 22:49 UTCGHSA enrichment
  8. 2026-08-18 13:48 UTCEPSS rescore
  9. 2026-08-18 11:56 UTCGHSA enrichment
  10. 2026-08-18 01:02 UTCGHSA enrichment
  11. 2026-08-17 14:08 UTCEG score recompute
  12. 2026-08-17 14:08 UTCGHSA enrichment
  13. 2026-08-17 03:15 UTCGHSA enrichment
  14. 2026-08-16 16:21 UTCEG score recompute
  15. 2026-08-16 16:21 UTCGHSA enrichment
  16. 2026-08-16 14:56 UTCEPSS rescore
  17. 2026-08-16 05:26 UTCEG score recompute
  18. 2026-08-16 05:26 UTCGHSA enrichment
  19. 2026-08-16 02:14 UTCEPSS rescore
  20. 2026-08-15 18:33 UTCGHSA enrichment
  21. 2026-08-15 07:39 UTCEG score recompute
  22. 2026-08-15 07:39 UTCGHSA enrichment
  23. 2026-08-15 01:30 UTCEPSS rescore
  24. 2026-08-14 20:45 UTCGHSA enrichment
  25. 2026-08-14 09:52 UTCGHSA enrichment
Show 35 more
  1. 2026-08-13 22:58 UTCEG score recompute
  2. 2026-08-13 22:58 UTCGHSA enrichment
  3. 2026-08-13 22:00 UTCEPSS rescore
  4. 2026-08-13 12:04 UTCGHSA enrichment
  5. 2026-08-13 01:10 UTCGHSA enrichment
  6. 2026-08-12 14:17 UTCEG score recompute
  7. 2026-08-12 14:17 UTCGHSA enrichment
  8. 2026-08-12 13:50 UTCEPSS rescore
  9. 2026-08-12 03:23 UTCGHSA enrichment
  10. 2026-08-11 16:29 UTCEG score recompute
  11. 2026-08-11 16:29 UTCGHSA enrichment
  12. 2026-08-11 13:42 UTCEPSS rescore
  13. 2026-08-11 05:35 UTCEG score recompute
  14. 2026-08-11 05:35 UTCGHSA enrichment
  15. 2026-08-10 23:59 UTCEPSS rescore
  16. 2026-08-10 18:42 UTCGHSA enrichment
  17. 2026-08-10 07:48 UTCGHSA enrichment
  18. 2026-08-09 20:55 UTCEG score recompute
  19. 2026-08-09 20:55 UTCGHSA enrichment
  20. 2026-08-09 13:46 UTCEPSS rescore
  21. 2026-08-09 10:01 UTCGHSA enrichment
  22. 2026-08-08 23:08 UTCEG score recompute
  23. 2026-08-08 23:08 UTCGHSA enrichment
  24. 2026-08-08 16:37 UTCEPSS rescore
  25. 2026-08-08 12:14 UTCGHSA enrichment
  26. 2026-08-08 01:20 UTCEG score recompute
  27. 2026-08-08 01:20 UTCGHSA enrichment
  28. 2026-08-07 14:27 UTCEG score recompute
  29. 2026-08-07 14:26 UTCGHSA enrichment
  30. 2026-08-07 14:13 UTCEG score recompute
  31. 2026-08-07 14:13 UTCGHSA enrichment
  32. 2026-08-07 09:11 UTCEG score recompute
  33. 2026-08-07 09:11 UTCGHSA enrichment
  34. 2026-08-06 22:18 UTCEG score recompute
  35. 2026-08-06 22:15 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-10599?
CVE-2026-10599 is a high vulnerability published on August 6, 2026. The Integrate PhonePe with WooCommerce WordPress plugin through 1.2.1 does not validate that a verified payment transaction belongs to the order being marked as paid, nor does it verify the authenticity of its payment-completion request, allowing unauthenticated attackers to reuse a single valid…
When was CVE-2026-10599 disclosed?
CVE-2026-10599 was first published in the National Vulnerability Database on August 6, 2026, with the most recent update on August 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-10599 actively exploited?
CVE-2026-10599 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 94.3% of all scored CVEs.
What is the CVSS score of CVE-2026-10599?
CVE-2026-10599 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-10599?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-10599, 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-10599

Explore →

Is Your Infrastructure Affected by CVE-2026-10599?

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

Start Free Scan →Browse All CVEs