CVE-2026-83537

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreHIGH confidence

Score 5.3 from GitHub Security Advisory published 2026-09-09. a secondary CVSS source baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
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 WP Express Checkout WordPress plugin before 2.5.0 does not verify server-side that a payment was actually completed before marking an order as paid, allowing unauthenticated users to forge a completed order without paying.

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

Published

September 9, 2026

Last Modified

September 9, 2026

Advisory Details (1)

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

WP Express Checkout < 2.5.0 – Unauthenticated Payment Bypass via wpec_process_empty_payment | CVE 2026-83537 | Plugin Vulnerabilities

https://wpscan.com/vulnerability/02b39e4f-181d-4573-9175-bf5a6d71e531/

Vendor Advisories for CVE-2026-83537(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 / 35× 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-09-19 15:59 UTCEG score recompute
  2. 2026-09-19 15:59 UTCGHSA enrichment
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-18 17:59 UTCGHSA enrichment
  5. 2026-09-17 20:15 UTCEG score recompute
  6. 2026-09-17 20:15 UTCGHSA enrichment
  7. 2026-09-17 19:32 UTCEPSS rescore
  8. 2026-09-16 22:30 UTCEG score recompute
  9. 2026-09-16 22:29 UTCGHSA enrichment
  10. 2026-09-16 14:09 UTCEPSS rescore
  11. 2026-09-16 05:15 UTCEPSS rescore
  12. 2026-09-16 00:45 UTCEG score recompute
  13. 2026-09-16 00:45 UTCGHSA enrichment
  14. 2026-09-15 03:12 UTCEPSS rescore
  15. 2026-09-15 03:12 UTCEPSS rescore
  16. 2026-09-15 03:01 UTCGHSA enrichment
  17. 2026-09-14 05:17 UTCEG score recompute
  18. 2026-09-14 05:17 UTCGHSA enrichment
  19. 2026-09-13 07:33 UTCEG score recompute
  20. 2026-09-13 07:33 UTCGHSA enrichment
  21. 2026-09-12 09:50 UTCEG score recompute
  22. 2026-09-12 09:50 UTCGHSA enrichment
  23. 2026-09-11 14:53 UTCEPSS rescore
  24. 2026-09-11 14:53 UTCEPSS rescore
  25. 2026-09-11 12:06 UTCGHSA enrichment
Show 10 more
  1. 2026-09-10 14:22 UTCEG score recompute
  2. 2026-09-10 14:22 UTCGHSA enrichment
  3. 2026-09-09 16:38 UTCGHSA enrichment
  4. 2026-09-09 15:49 UTCEG score recompute
  5. 2026-09-09 15:49 UTCGHSA enrichment
  6. 2026-09-09 15:35 UTCEG score recompute
  7. 2026-09-09 15:35 UTCGHSA enrichment
  8. 2026-09-09 07:20 UTCEG score recompute
  9. 2026-09-09 06:38 UTCEG score recompute
  10. 2026-09-09 06:38 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-83537?
CVE-2026-83537 is a medium vulnerability published on September 9, 2026. The WP Express Checkout WordPress plugin before 2.5.0 does not verify server-side that a payment was actually completed before marking an order as paid, allowing unauthenticated users to forge a completed order without paying.
When was CVE-2026-83537 disclosed?
CVE-2026-83537 was first published in the National Vulnerability Database on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-83537 actively exploited?
CVE-2026-83537 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 98.3% of all scored CVEs.
What is the CVSS score of CVE-2026-83537?
CVE-2026-83537 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-83537?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-83537, 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-83537

Explore →

Is Your Infrastructure Affected by CVE-2026-83537?

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

Start Free Scan →Browse All CVEs