CVE-2026-66479

HIGHPre-NVD 7.17.1—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.1EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: <0.1%CVSS: 7.1Exploit: None knownExposed services: Not assessed

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

Cross-Site Request Forgery (CSRF) vulnerability in Liquid Web / StellarWP WPComplete wpcomplete allows Stored XSS.This issue affects WPComplete: from n/a through 2.9.5.6.

CVSS v3
7.1
EG Score
7.1HIGHhigh confidence
EG Risk
32
EG Risk 32/100CISA SSVC

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
Severity71% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
<0.1%
EPSS %ILE
below the 1st
KEV
Not listed

CISA SSVCTrack at every mission impact level.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

October 8, 2026

Last Modified

October 8, 2026

Advisory Details (1)

Auto-updated Oct 8, 2026
No fix on record yet.

Vendor Advisories for CVE-2026-66479(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 16× in last 7d / 16× 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-11 04:57 UTCEG score recompute
  2. 2026-10-11 04:57 UTCGHSA enrichmentGHSA-vhxj-w8cf-84xv · GitHub severity HIGH · GitHub CVSS 7.1
  3. 2026-10-10 20:00 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  4. 2026-10-10 17:02 UTCGHSA enrichmentGHSA-vhxj-w8cf-84xv · GitHub severity HIGH · GitHub CVSS 7.1
  5. 2026-10-10 05:08 UTCEG score recompute
  6. 2026-10-10 05:07 UTCGHSA enrichmentGHSA-vhxj-w8cf-84xv · GitHub severity HIGH · GitHub CVSS 7.1
  7. 2026-10-09 20:07 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  8. 2026-10-09 17:14 UTCGHSA enrichmentGHSA-vhxj-w8cf-84xv · GitHub severity HIGH · GitHub CVSS 7.1
  9. 2026-10-09 05:21 UTCGHSA enrichmentGHSA-vhxj-w8cf-84xv · GitHub severity HIGH · GitHub CVSS 7.1
  10. 2026-10-08 17:27 UTCEG score recompute
  11. 2026-10-08 17:26 UTCGHSA enrichmentGHSA-vhxj-w8cf-84xv · GitHub severity HIGH · GitHub CVSS 7.1
  12. 2026-10-08 15:23 UTCEG score recompute
  13. 2026-10-08 14:46 UTCEG score recompute
  14. 2026-10-08 13:33 UTCEG score recompute
  15. 2026-10-08 12:37 UTCEG score recompute
  16. 2026-10-08 12:36 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-66479?
CVE-2026-66479 is a high vulnerability published on October 8, 2026. Cross-Site Request Forgery (CSRF) vulnerability in Liquid Web / StellarWP WPComplete wpcomplete allows Stored XSS.This issue affects WPComplete: from n/a through 2.9.5.6.
When was the CVE record for CVE-2026-66479 published?
The CVE record for CVE-2026-66479 was published on October 8, 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 8, 2026; the record at its source may have been updated since.
Is CVE-2026-66479 actively exploited?
CVE-2026-66479 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a <0.1% probability of exploitation in the next 30 days (below the 1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-66479?
CVE-2026-66479 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-66479?
No fix for CVE-2026-66479 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 vendor advisories EchelonGraph has for CVE-2026-66479 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-66479?

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