CVE-2026-97670

CRITICALPre-NVD 9.19.1
EchelonGraph scoreHIGH confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week
9.1EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 9.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.

The CVE record's CNA (Wordfence) lists themefusion Avada (Fusion) Builder versions up to and including 7.16.1 as affected. No release containing a fix is confirmed on record.

The Avada (Fusion) Builder plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 7.16.1. This is due to the plugin not properly verifying authorization before dispatching a WordPress action hook whose name is taken from an attacker-supplied form-field value (via the notification email_message [field] placeholder and the {action_hook,...} dynamic-data token; the 3.16.1 trust gate is_content_request_supplied() only inspects $_POST['args']/$_GET['args'], never the $_POST['formData'] the public form-submit endpoint parses). This makes it possible for unauthenticated attackers to invoke arbitrary WordPress action hooks (multiple per request), causing state changes up to permanent, irreversible destruction of site content: a verified unauthenticated request permanently deleted trashed posts, pages, and comments via the core wp_scheduled_delete action. Other non-deny-listed hooks extend the impact to denial of service (e.g. wp_maybe_auto_update) and, where vulnerable third-party handlers are installed, further privileged writes. The same unauthenticated dynamic-data pipeline additionally exposes a blind arbitrary user/post-meta read; the read result is delivered only to the site owner and is not attacker-exfiltrable through the plugin's own email/response paths. Exploitation requires a published Avada form with AJAX submission and a notification whose email_message template includes an [all_fields] or explicit [field] placeholder - the default form configuration.

CVSS v3
9.1
EG Score
9.1CRITICALhigh confidence
EG Risk
56
EG Risk 56/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)
Severity91% × 45%
The EG Score, 9.1 of 10.
Exploitation0.4% × 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.4%
EPSS %ILE
28th
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 10, 2026

Last Modified

October 13, 2026

Advisory Details (1)

Auto-updated Oct 10, 2026
No fix on record yet.
Web page

Version 7.16.2 Security Update – Avada Website Builder

https://avada.com/blog/version-7-16-2-security-update/

Vendor Advisories for CVE-2026-97670(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 33× in last 7d / 33× 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:35 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  2. 2026-10-13 13:45 UTCGHSA enrichmentGHSA-wc6q-34rr-pv23 · GitHub severity CRITICAL · GitHub CVSS 9.1
  3. 2026-10-12 21:29 UTCEG score recompute
  4. 2026-10-12 21:29 UTCGHSA enrichmentGHSA-wc6q-34rr-pv23 · GitHub severity CRITICAL · GitHub CVSS 9.1
  5. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  6. 2026-10-12 14:39 UTCEG score recompute
  7. 2026-10-12 04:46 UTCGHSA enrichmentGHSA-wc6q-34rr-pv23 · GitHub severity CRITICAL · GitHub CVSS 9.1
  8. 2026-10-12 01:04 UTCGHSA enrichmentGHSA-wc6q-34rr-pv23 · GitHub severity CRITICAL · GitHub CVSS 9.1
  9. 2026-10-11 21:20 UTCGHSA enrichmentGHSA-wc6q-34rr-pv23 · GitHub severity CRITICAL · GitHub CVSS 9.1
  10. 2026-10-11 19:10 UTCEG score recompute
  11. 2026-10-11 17:36 UTCEG score recompute
  12. 2026-10-11 17:36 UTCGHSA enrichmentGHSA-wc6q-34rr-pv23 · GitHub severity CRITICAL · GitHub CVSS 9.1
  13. 2026-10-11 17:02 UTCEG score recompute
  14. 2026-10-11 17:02 UTCGHSA enrichmentGHSA-wc6q-34rr-pv23 · GitHub severity CRITICAL · GitHub CVSS 9.1
  15. 2026-10-11 16:26 UTCEG score recompute
  16. 2026-10-11 14:33 UTCEG score recompute
  17. 2026-10-11 14:33 UTCGHSA enrichmentGHSA-wc6q-34rr-pv23 · GitHub severity CRITICAL · GitHub CVSS 9.1
  18. 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  19. 2026-10-11 13:38 UTCEG score recompute
  20. 2026-10-11 10:51 UTCGHSA enrichmentGHSA-wc6q-34rr-pv23 · GitHub severity CRITICAL · GitHub CVSS 9.1
  21. 2026-10-11 07:09 UTCGHSA enrichmentGHSA-wc6q-34rr-pv23 · GitHub severity CRITICAL · GitHub CVSS 9.1
  22. 2026-10-11 03:27 UTCGHSA enrichmentGHSA-wc6q-34rr-pv23 · GitHub severity CRITICAL · GitHub CVSS 9.1
  23. 2026-10-10 23:45 UTCGHSA enrichmentGHSA-wc6q-34rr-pv23 · GitHub severity CRITICAL · GitHub CVSS 9.1
  24. 2026-10-10 20:04 UTCEG score recompute
  25. 2026-10-10 20:04 UTCGHSA enrichmentGHSA-wc6q-34rr-pv23 · GitHub severity CRITICAL · GitHub CVSS 9.1
Show 8 more
  1. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  2. 2026-10-10 16:23 UTCGHSA enrichmentGHSA-wc6q-34rr-pv23 · GitHub severity CRITICAL · GitHub CVSS 9.1
  3. 2026-10-10 12:42 UTCGHSA enrichmentGHSA-wc6q-34rr-pv23 · GitHub severity CRITICAL · GitHub CVSS 9.1
  4. 2026-10-10 09:01 UTCEG score recompute
  5. 2026-10-10 09:01 UTCGHSA enrichmentGHSA-wc6q-34rr-pv23 · GitHub severity CRITICAL · GitHub CVSS 9.1
  6. 2026-10-10 05:21 UTCEG score recompute
  7. 2026-10-10 04:31 UTCEG score recomputeFirst assessed: 9.1 CRITICAL
  8. 2026-10-10 04:30 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-97670?
CVE-2026-97670 is a critical-severity vulnerability; its CVE record was published on October 10, 2026. The Avada (Fusion) Builder plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 7.16.1. This is due to the plugin not properly verifying authorization before dispatching a WordPress action hook whose name is taken from an attacker-supplied form-field…
When was the CVE record for CVE-2026-97670 published?
The CVE record for CVE-2026-97670 was published on October 10, 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 13, 2026; the record at its source may have been updated since.
Is CVE-2026-97670 actively exploited?
CVE-2026-97670 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (28th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-97670?
CVE-2026-97670 has a CVSS base score of 9.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-97670?
No fix for CVE-2026-97670 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 (Wordfence) lists themefusion Avada (Fusion) Builder versions up to and including 7.16.1 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-97670 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-97670?

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

Book a Demo →Browse All CVEs