CVE-2026-84043

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreHIGH confidence

Score 5.3 from GitHub Security Advisory published 2026-09-04. 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 ePayco Payment Gateway for WooCommerce WordPress plugin before 8.4.7 does not properly verify the authenticity of payment confirmation requests, allowing unauthenticated attackers to mark orders as paid without a valid gateway signature.

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 4, 2026

Last Modified

September 8, 2026

Advisory Details (1)

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

ePayco Payment Gateway for WooCommerce < 8.4.7 – Unauthenticated Payment Confirmation Bypass | CVE 2026-84043 | Plugin Vulnerabilities

https://wpscan.com/vulnerability/96599654-1d7f-4ff0-a4b4-26e540375a67/

Vendor Advisories for CVE-2026-84043(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 / 47× 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 20:59 UTCEG score recompute
  2. 2026-09-19 20:59 UTCGHSA enrichment
  3. 2026-09-18 22:59 UTCEG score recompute
  4. 2026-09-18 22:59 UTCGHSA enrichment
  5. 2026-09-18 19:28 UTCEPSS rescore
  6. 2026-09-18 01:00 UTCEG score recompute
  7. 2026-09-18 01:00 UTCGHSA enrichment
  8. 2026-09-17 19:32 UTCEPSS rescore
  9. 2026-09-17 03:00 UTCEG score recompute
  10. 2026-09-17 03:00 UTCGHSA enrichment
  11. 2026-09-16 14:09 UTCEPSS rescore
  12. 2026-09-16 05:15 UTCEPSS rescore
  13. 2026-09-16 04:29 UTCGHSA enrichment
  14. 2026-09-15 06:14 UTCEG score recompute
  15. 2026-09-15 06:14 UTCGHSA enrichment
  16. 2026-09-15 03:12 UTCEPSS rescore
  17. 2026-09-15 03:12 UTCEPSS rescore
  18. 2026-09-14 08:14 UTCEG score recompute
  19. 2026-09-14 08:14 UTCGHSA enrichment
  20. 2026-09-13 10:15 UTCGHSA enrichment
  21. 2026-09-12 12:15 UTCEG score recompute
  22. 2026-09-12 12:15 UTCGHSA enrichment
  23. 2026-09-11 14:53 UTCEPSS rescore
  24. 2026-09-11 14:53 UTCEPSS rescore
  25. 2026-09-11 14:15 UTCEG score recompute
Show 22 more
  1. 2026-09-11 14:15 UTCGHSA enrichment
  2. 2026-09-10 16:16 UTCEG score recompute
  3. 2026-09-10 16:15 UTCGHSA enrichment
  4. 2026-09-09 17:57 UTCEG score recompute
  5. 2026-09-09 17:57 UTCGHSA enrichment
  6. 2026-09-08 22:01 UTCEPSS rescore
  7. 2026-09-08 19:57 UTCGHSA enrichment
  8. 2026-09-08 12:53 UTCGHSA enrichment
  9. 2026-09-07 14:46 UTCGHSA enrichment
  10. 2026-09-06 15:21 UTCEG score recompute
  11. 2026-09-06 15:21 UTCGHSA enrichment
  12. 2026-09-06 13:48 UTCEPSS rescore
  13. 2026-09-05 17:21 UTCEG score recompute
  14. 2026-09-05 17:20 UTCGHSA enrichment
  15. 2026-09-05 15:31 UTCEPSS rescore
  16. 2026-09-04 19:19 UTCEG score recompute
  17. 2026-09-04 19:19 UTCGHSA enrichment
  18. 2026-09-04 18:40 UTCEG score recompute
  19. 2026-09-04 18:40 UTCGHSA enrichment
  20. 2026-09-04 10:31 UTCEG score recompute
  21. 2026-09-04 10:04 UTCEG score recompute
  22. 2026-09-04 10:03 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-84043?
CVE-2026-84043 is a medium vulnerability published on September 4, 2026. The ePayco Payment Gateway for WooCommerce WordPress plugin before 8.4.7 does not properly verify the authenticity of payment confirmation requests, allowing unauthenticated attackers to mark orders as paid without a valid gateway signature.
When was CVE-2026-84043 disclosed?
CVE-2026-84043 was first published in the National Vulnerability Database on September 4, 2026, with the most recent update on September 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-84043 actively exploited?
CVE-2026-84043 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-84043?
CVE-2026-84043 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-84043?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-84043, 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-84043

Explore →

Is Your Infrastructure Affected by CVE-2026-84043?

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

Start Free Scan →Browse All CVEs