CVE-2026-42637

MEDIUMPre-NVD 6.56.5
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 6.5 from GitHub Security Advisory published 2026-10-06. A secondary CVSS source baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this week
6.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 6.5Exploit: None knownExposed services: Not assessed

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

The CVE record's CNA (Patchstack) lists PayPlug for WooCommerce (Official) versions up to and including 3.1.0 as affected. No release containing a fix is confirmed on record.

Unauthenticated Settings Change in PayPlug for WooCommerce (Official) <= 3.1.0 versions.

CVSS v3
6.5
EG Score
6.5MEDIUMhigh confidence
EG Risk
44
EG Risk 44/100

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 (value × EchelonGraph’s weight)
Severity65% × 45%
The EG Score, 6.5 of 10.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.3%
EPSS %ILE
24th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 6, 2026

Last Modified

October 6, 2026

Advisory Details (1)

Auto-updated Oct 6, 2026
No fix on record yet.
Web pageMentions a patch (unverified)

Settings Change in WordPress PayPlug for WooCommerce (Official) Plugin - Patchstack

https://patchstack.com/database/wordpress/plugin/payplug/vulnerability/wordpress-payplug-for-woocommerce-official-plugin-3-1-0-settings-change-vulnerability?_s_id=cve

Vendor Advisories for CVE-2026-42637(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 19× in last 7d / 30× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  3. 2026-10-12 16:07 UTCEG score recompute
  4. 2026-10-12 03:09 UTCGHSA enrichmentGHSA-28x2-x4c5-mp8x · GitHub CVSS 6.5
  5. 2026-10-11 19:49 UTCEG score recompute
  6. 2026-10-11 17:03 UTCEG score recompute
  7. 2026-10-11 14:29 UTCEG score recompute
  8. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  9. 2026-10-11 00:46 UTCEG score recompute
  10. 2026-10-11 00:46 UTCGHSA enrichmentGHSA-28x2-x4c5-mp8x · GitHub CVSS 6.5
  11. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  12. 2026-10-09 22:24 UTCEG score recompute
  13. 2026-10-09 22:24 UTCGHSA enrichmentGHSA-28x2-x4c5-mp8x · GitHub CVSS 6.5
  14. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  15. 2026-10-08 20:04 UTCEG score recompute
  16. 2026-10-08 20:04 UTCGHSA enrichmentGHSA-28x2-x4c5-mp8x · GitHub CVSS 6.5
  17. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  18. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  19. 2026-10-07 17:39 UTCGHSA enrichmentGHSA-28x2-x4c5-mp8x · GitHub CVSS 6.5
  20. 2026-10-06 15:19 UTCEG score recompute
  21. 2026-10-06 15:19 UTCGHSA enrichmentGHSA-28x2-x4c5-mp8x · GitHub CVSS 6.5
  22. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  23. 2026-10-06 11:28 UTCEG score recompute
  24. 2026-10-06 11:28 UTCGHSA enrichmentGHSA-28x2-x4c5-mp8x · GitHub CVSS 6.5
  25. 2026-10-06 10:45 UTCEG score recompute
Show 5 more
  1. 2026-10-06 10:45 UTCGHSA enrichmentGHSA-28x2-x4c5-mp8x · GitHub CVSS 6.5
  2. 2026-10-06 09:58 UTCEG score recompute
  3. 2026-10-06 09:58 UTCGHSA enrichmentGHSA-28x2-x4c5-mp8x · GitHub CVSS 6.5
  4. 2026-10-06 08:52 UTCEG score recomputeFirst assessed: 6.5 MEDIUM
  5. 2026-10-06 08:52 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-42637?
CVE-2026-42637 is a medium-severity vulnerability; its CVE record was published on October 6, 2026. Unauthenticated Settings Change in PayPlug for WooCommerce (Official) <= 3.1.0 versions.
When was the CVE record for CVE-2026-42637 published?
The CVE record for CVE-2026-42637 was published on October 6, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 6, 2026; the record at its source may have been updated since.
Is CVE-2026-42637 actively exploited?
CVE-2026-42637 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (24th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-42637?
CVE-2026-42637 has a CVSS base score of 6.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-42637?
No fix for CVE-2026-42637 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (Patchstack) lists PayPlug for WooCommerce (Official) versions up to and including 3.1.0 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-42637 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-42637

Explore →

Is Your Infrastructure Affected by CVE-2026-42637?

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

Book a Demo →Browse All CVEs