Groundhogg — CRM, Newsletters, and Marketing Automation <= 4.4 - Authenticated (Sales Representative+) Arbitrary File Deletion
Strategic Overview
- Status
- Patched in 4.4.1
- Affected Plugin
- Groundhogg — CRM, Newsletters, and Marketing Automation
- Affected Version
<= 4.4- CVSS
- 8.1High
- Weakness type
- CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
- CVE
CVE-2026-40727
At a glance
CVE-2026-40727 is a high-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the Groundhogg WordPress plugin, affecting versions <= 4.4. It carries a CVSS score of 8.1 (reachable over the network; low attack complexity; high integrity, availability impact). Exploitation requires an authenticated account at Sales Representative level or above. The issue is fixed in version 4.4.1; sites on affected versions should update now. Disclosed April 2026, reported by daroo.
Vulnerability Overview
The Groundhogg — CRM, Newsletters, and Marketing Automation plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in all versions up to, and including, 4.4. This makes it possible for authenticated attackers, with Custom-level access and above, to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php).
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on integrity, availability.
CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Reaching this weakness in Groundhogg <= 4.4 takes an account at Sales Representative level or above. Path traversal happens when user-controlled text is used to build a filesystem path without being constrained to an intended directory, so sequences like ../ walk the resolved path somewhere else.
Depending on the operation, it means reading files outside the intended folder — wp-config.php being the usual target — or writing to and deleting paths the web server can touch. For Groundhogg the fix is 4.4.1: builds <= 4.4 are affected, anything from 4.4.1 onward is not.
Remediation
Update to version 4.4.1, or a newer patched version
How does WordSec protect against this?
An attacker needs Sales Representative access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Groundhogg 4.4.1 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Groundhogg — CRM, Newsletters, and Marketing Automation
- 8.8CVE-2025-48300: Groundhogg <= 4.2.1 Arbitrary File Upload
CVE-2025-48300 - 8.8CVE-2025-0394: Groundhogg <= 3.7.3.5 Arbitrary File Upload
CVE-2025-0394 - 8.8Groundhogg <= 1.3.11.13 SQL Injection
- 8.8CVE-2019-15647: WordPress CRM RCE
CVE-2019-15647 - 7.5CVE-2025-54053: Groundhogg <= 4.2.2 PHP Object Injection
CVE-2025-54053 - 7.5CVE-2023-2736: Groundhogg <= 2.7.9.8 CSRF to Privilege Escalation
CVE-2023-2736 - 7.2CVE-2023-34179: Groundhogg <= 2.7.11 SQL Injection
CVE-2023-34179 - 7.2CVE-2023-1425: Groundhogg <= 2.7.9.3 + SQL Injection
CVE-2023-1425
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C