CVE-2026-92975

HIGHPre-NVD 8.18.1
EchelonGraph scoreHIGH confidence

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

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-10-10. A secondary CVSS source baseline 8.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
8.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

The Groundhogg — CRM, Newsletters, and Marketing Automation plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 4.8.3 via the create_support_user() function. This is due to the function identifying the support account solely by matching against publicly hardcoded constants — user_login 'groundhogg' and email addresses '[email protected]' / '[email protected]' — where the in_array() email-equality check at line 238 is not a security boundary because any user fully controls their own email value. This makes it possible for an attacker with an account whose user_login is 'groundhogg' and whose user_email matches one of the hardcoded support constants to have that account silently promoted to administrator — and additionally to super admin on multisite when the triggering administrator holds manage_network_options — resulting in full site takeover. Exploitation requires a two-actor flow: the attacker must first obtain or pre-plant an account with the hardcoded credentials (possible when open user registration is enabled or another account-creation path exists), after which a legitimate administrator must invoke the support-access feature via the submit_ticket or process_send_support_access entry points to trigger the promotion.

CVSS v3
8.1
EG Score
8.1HIGHhigh confidence
EG Risk
37
EG Risk 37/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)
Severity81% × 45%
The EG Score, 8.1 of 10.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
26th
KEV
Not listed

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

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (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 11, 2026

Advisory Details (1)

Auto-updated Oct 10, 2026
Patch available. Sources: github_commit.
GitHub commit Patch Available

commit 4b413aa6e (groundhoggwp/groundhogg)

Patch available: groundhoggwp/groundhogg 4.9.rc.1 (contains commit 4b413aa6e)

https://github.com/groundhoggwp/groundhogg/commit/4b413aa6e

Vendor Advisories for CVE-2026-92975(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 19:12 UTCEG score recompute
  2. 2026-10-11 17:35 UTCEG score recompute
  3. 2026-10-11 17:34 UTCGHSA enrichmentGHSA-7cvm-g94w-xfg7 · GitHub severity HIGH · GitHub CVSS 8.1
  4. 2026-10-11 17:01 UTCEG score recompute
  5. 2026-10-11 17:01 UTCGHSA enrichmentGHSA-7cvm-g94w-xfg7 · GitHub severity HIGH · GitHub CVSS 8.1
  6. 2026-10-11 16:29 UTCEG score recompute
  7. 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  8. 2026-10-11 13:43 UTCEG score recompute
  9. 2026-10-11 07:33 UTCEG score recompute
  10. 2026-10-11 07:33 UTCGHSA enrichmentGHSA-7cvm-g94w-xfg7 · GitHub severity HIGH · GitHub CVSS 8.1
  11. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  12. 2026-10-10 18:59 UTCEG score recompute
  13. 2026-10-10 18:59 UTCGHSA enrichmentGHSA-7cvm-g94w-xfg7 · GitHub severity HIGH · GitHub CVSS 8.1
  14. 2026-10-10 06:22 UTCEG score recompute
  15. 2026-10-10 05:35 UTCEG score recomputeFirst assessed: 8.1 HIGH
  16. 2026-10-10 05:35 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-92975?
CVE-2026-92975 is a high-severity vulnerability; its CVE record was published on October 10, 2026. The Groundhogg — CRM, Newsletters, and Marketing Automation plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 4.8.3 via the createsupportuser() function. This is due to the function identifying the support account solely by matching against publicly…
When was the CVE record for CVE-2026-92975 published?
The CVE record for CVE-2026-92975 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 11, 2026; the record at its source may have been updated since.
Is CVE-2026-92975 actively exploited?
CVE-2026-92975 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (26th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-92975?
CVE-2026-92975 has a CVSS base score of 8.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-92975?
A fix for CVE-2026-92975 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-92975 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-92975?

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

Book a Demo →Browse All CVEs