# CVE-2023-2717: Groundhogg <= 2.7.9.8 - Cross-Site Request Forgery to Disable All Plugins

> Unauthenticated attackers can disable all plugins via CSRF by tricking admins into clicking a link, causing service disruption.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 20 May 2023
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-m9rg-g68w-jqgv

## What is CVE-2023-2717?

CVE-2023-2717 is a medium-severity vulnerability in trainingbusinesspros Groundhogg — CRM, Newsletters, and Marketing Automation, published on 20 May 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The Groundhogg plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.7.9.8. This is due to missing nonce validation on the 'enable_safe_mode' function. This makes it possible for unauthenticated attackers to enable safe mode, which disables all other plugins, via a forged request if they can successfully trick an administrator into performing an action such as clicking on a link. A warning message about safe mode is displayed to the admin, which can be easily disabled.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2023-2717?

It affects 1 product.


Products: Groundhogg Groundhogg.

## How do I fix CVE-2023-2717?

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

## Is CVE-2023-2717 being exploited?

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

## Other vulnerabilities in trainingbusinesspros Groundhogg — CRM, Newsletters, and Marketing Automation

- [CVE-2019-15647](https://insights.sbomify.com/CVE-2019-15647/): The groundhogg plugin before 1.3.5 for WordPress has wp-admin/admin-ajax.php?action=bulk_action_listener remote code execution. (high 8.8)
- [CVE-2023-34179](https://insights.sbomify.com/CVE-2023-34179/): WordPress Groundhogg Plugin <= 2.7.11 is vulnerable to SQL Injection (high 7.6)
- [CVE-2023-2736](https://insights.sbomify.com/CVE-2023-2736/): Groundhogg <= 2.7.9.8 - Cross-Site Request Forgery to Privilege Escalation (high 7.5)
- [CVE-2023-1425](https://insights.sbomify.com/CVE-2023-1425/): Groundhogg Contacts < 2.7.9.4 - Admin+ SQLi (high 7.2)
- [CVE-2024-37264](https://insights.sbomify.com/CVE-2024-37264/): WordPress Groundhogg plugin <= 3.4.2.3 - Reflected Cross Site Scripting (XSS) vulnerability (high 7.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-2717 and fix it if it is affected.

What it is: CVE-2023-2717 is a medium-severity vulnerability in trainingbusinesspros Groundhogg — CRM, Newsletters, and Marketing Automation, published on 20 May 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-2717 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-2023-2717/ (Markdown: https://insights.sbomify.com/CVE-2023-2717/index.md)
```

## Sources

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

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