# CVE-2026-92975: Groundhogg <= 4.8.3 - Unauthenticated Privilege Escalation to Support User Identity Confusion

> Attackers can escalate privileges to administrator by exploiting hardcoded support user checks, requiring open registration and admin interaction.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Oct 2026
- **Updated:** 11 Oct 2026
- **Also known as:** GHSA-7cvm-g94w-xfg7

## What is CVE-2026-92975?

CVE-2026-92975 is a high-severity vulnerability in trainingbusinesspros Groundhogg — CRM, Newsletters, and Marketing Automation, published on 10 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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 `'support@groundhogg.io'` / `'help@groundhogg.io'` — 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.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2026-92975?


## How do I fix CVE-2026-92975?

No fix has been published for CVE-2026-92975 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-92975 being exploited?

There is no known exploitation of CVE-2026-92975 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-92975 and fix it if it is affected.

What it is: CVE-2026-92975 is a high-severity vulnerability in trainingbusinesspros Groundhogg — CRM, Newsletters, and Marketing Automation, published on 10 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-92975 in the wild and no public exploit code.

Affected product: trainingbusinesspros Groundhogg — CRM, Newsletters, and Marketing Automation. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-92975/ (Markdown: https://insights.sbomify.com/CVE-2026-92975/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-92975
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-92975
- OSV: https://osv.dev/vulnerability/CVE-2026-92975

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-92975/
Summaries are generated and may contain mistakes; the official description above is the record.