The Groundhogg — CRM, Newsletters, and Marketing Automation plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 4.9 This is due to a missing ownership and capability check on the user parameter within the process_edit() function, which allows any authenticated user with the edit_contacts capability to reassign a contact record's linked WordPress user ID to any arbitrary account without requiring the edit_users or promote_users capabilities. This makes it possible for authenticated attackers, with sales_rep-level access and above, to escalate their privileges to administrator by linking a contact to an administrator's WordPress user ID, then creating a note containing the {auto_login_link} replacement tag to trigger generation of a valid auto-login permissions-key URL for the administrator-linked contact, and finally visiting that URL to authenticate as the targeted administrator. The auto-login URL is stored in the note content and is readable back by the attacker via the view_notes and add_notes capabilities that the sales_rep role holds by default.
CVE-2026-104725
“—” beside the score: it is equal to the CVSS score beside it.
Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-10-10. A secondary CVSS source baseline 8.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 8.8
- EG Score
- 8.8HIGHhigh confidence
- EG Risk
- 40EG Risk 40/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)Severity88% × 45%The EG Score, 8.8 of 10.Exploitation0.3% × 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 every mission impact level.Exploitation none (CISA Vulnrichment) · Automatable no (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: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.3%
- EPSS %ILE
- 24th
- KEV
- Not listed
SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (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)60 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 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 11, 2026
Advisory Details (1)
Auto-updated Oct 10, 2026commit 804abf42a (groundhoggwp/groundhogg)
Patch available: groundhoggwp/groundhogg 4.9.1 (contains commit 804abf42a)
https://github.com/groundhoggwp/groundhogg/commit/804abf42aVendor Advisories for CVE-2026-104725(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 15× in last 7d / 15× 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.
- 2026-10-11 20:15 UTCEG score recompute
- 2026-10-11 17:35 UTCEG score recompute
- 2026-10-11 17:35 UTCGHSA enrichmentGHSA-p495-v7fq-hqr5 · GitHub severity HIGH · GitHub CVSS 8.8
- 2026-10-11 17:01 UTCEG score recompute
- 2026-10-11 17:01 UTCGHSA enrichmentGHSA-p495-v7fq-hqr5 · GitHub severity HIGH · GitHub CVSS 8.8
- 2026-10-11 15:01 UTCEG score recompute
- 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-10-11 06:20 UTCEG score recompute
- 2026-10-11 06:19 UTCGHSA enrichmentGHSA-p495-v7fq-hqr5 · GitHub severity HIGH · GitHub CVSS 8.8
- 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-10-10 18:21 UTCEG score recompute
- 2026-10-10 18:21 UTCGHSA enrichmentGHSA-p495-v7fq-hqr5 · GitHub severity HIGH · GitHub CVSS 8.8
- 2026-10-10 06:23 UTCEG score recompute
- 2026-10-10 05:35 UTCEG score recomputeFirst assessed: 8.8 HIGH
- 2026-10-10 05:35 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-104725?
When was the CVE record for CVE-2026-104725 published?
Is CVE-2026-104725 actively exploited?
What is the CVSS score of CVE-2026-104725?
How do I remediate CVE-2026-104725?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-104725
Is Your Infrastructure Affected by CVE-2026-104725?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.