The SUMIT Payment Gateway for WooCommerce WordPress plugin before 4.0.0 does not verify with the payment provider that a payment notification is genuine before marking the corresponding order as paid, allowing unauthenticated users to mark a pending order paid without completing payment.
CVE-2026-84091
This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.3
- EG Score
- 5.3(low)
- EG Risk
- 55(Attend)EG Risk 55/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 computedSeverity53% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
September 23, 2026
Last Modified
September 23, 2026
Advisory Details (1)
Auto-updated Sep 23, 2026SUMIT Payment Gateway for WooCommerce < 4.0.0 – Unauthenticated Payment Confirmation Forgery via bit IPN | CVE 2026-84091 | Plugin Vulnerabilities
https://wpscan.com/vulnerability/10c7a9bd-eac0-49eb-9238-d7c477312166/Vendor Advisories for CVE-2026-84091(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 4× in last 7d / 4× 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.
- 2026-09-23 13:18 UTCEG score recompute
- 2026-09-23 12:46 UTCEG score recompute
- 2026-09-23 12:21 UTCEG score recompute
- 2026-09-23 12:20 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-287
Frequently asked(4)
What is CVE-2026-84091?
When was CVE-2026-84091 disclosed?
What is the CVSS score of CVE-2026-84091?
How do I remediate CVE-2026-84091?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-84091
Is Your Infrastructure Affected by CVE-2026-84091?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.