HomeWordPress vulnerabilitiesGroundhogg
Groundhogg vulnerabilities
Groundhogg has 23 known vulnerabilities in this database. The most recent published record is dated 6 Oct 2026.
- Known vulnerabilities
- 23
- Active installs
- 2,000+
- Latest version
- 4.8.3
- Last updated
- 18 Sep 2026
- Most recent
- 6 Oct 2026
No fixed version has been published yet, so consider disabling, removing or replacing the plugin until a safe release is available.
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Sensitive data exposure CVE-2026-104385 | High 7.5 | Up to 4.8.3 | No fixed version yet | 1 d ago |
| SQL injection CVE-2026-104408 | High 7.6 | Up to 4.8.3 | No fixed version yet | 2 d ago |
| Privilege escalation CVE-2026-97644 | High 8.8 | Up to 4.9 | No fixed version yet | 4 d ago |
| Open redirect CVE-2026-81741 | Medium 4.7 | Before 4.7.2 | Fixed in 4.7.2 | 9 Sep 2026 |
| Cross-site scripting (XSS) CVE-2026-81660 | High 8.8 | Before 4.5.13 | Fixed in 4.5.13 | 30 Aug 2026 |
| SQL injection CVE-2026-18387 | Medium 6.5 | Up to 4.5.14 | Fixed in a later version (latest 4.8.3) | 15 Aug 2026 |
| Broken access control CVE-2026-11454 | Medium 6.5 | Up to 4.5.2 | Fixed in a later version (latest 4.8.3) | 5 Aug 2026 |
| SQL injection CVE-2026-14029 | Medium 6.5 | Up to 4.5.8 | Fixed in a later version (latest 4.8.3) | 2 Jul 2026 |
| SQL injection CVE-2026-13331 | Medium 6.5 | Up to 4.5.5 | Fixed in a later version (latest 4.8.3) | 27 Jun 2026 |
| SQL injection CVE-2026-13333 | Medium 6.5 | Up to 4.5.5 | Fixed in a later version (latest 4.8.3) | 27 Jun 2026 |
| SQL injection CVE-2026-13226 | Medium 6.5 | Up to 4.5.4 | Fixed in a later version (latest 4.8.3) | 26 Jun 2026 |
| SQL injection CVE-2025-12750 | Medium 4.9 | Up to 4.2.6.1 | Fixed in a later version (latest 4.8.3) | 21 Nov 2025 |
| Remote code execution CVE-2025-4206 | High 7.2 | Up to 4.1.1.2 | Fixed in a later version (latest 4.8.3) | 9 May 2025 |
| Cross-site scripting (XSS) CVE-2025-1267 | Medium 5.5 | Up to 3.7.4.1 | Fixed in a later version (latest 4.8.3) | 1 Apr 2025 |
| Remote code execution CVE-2025-0394 | High 8.8 | Up to 3.7.3.5 | Fixed in a later version (latest 4.8.3) | 14 Jan 2025 |
| Broken access control CVE-2023-2715 | Medium 4.3 | Up to 2.7.9.8 | Fixed in a later version (latest 4.8.3) | 20 May 2023 |
| Broken access control CVE-2023-2716 | Medium 5.4 | Up to 2.7.9.8 | Fixed in a later version (latest 4.8.3) | 20 May 2023 |
| Cross-site request forgery (CSRF) CVE-2023-2717 | Medium 5.4 | Up to 2.7.9.8 | Fixed in a later version (latest 4.8.3) | 20 May 2023 |
| Cross-site scripting (XSS) CVE-2023-2735 | Medium 4.9 | Up to 2.7.9.8 | Fixed in a later version (latest 4.8.3) | 20 May 2023 |
| Cross-site request forgery (CSRF) CVE-2023-2736 | High 7.5 | Up to 2.7.9.8 | Fixed in a later version (latest 4.8.3) | 20 May 2023 |
| Broken access control CVE-2023-2714 | Medium 4.3 | Up to 2.7.9.8 | Fixed in a later version (latest 4.8.3) | 20 May 2023 |
| SQL injection CVE-2023-1425 | High 7.2 | Before 2.7.9.4 | Fixed in 2.7.9.4 | 10 Apr 2023 |
| Remote code execution CVE-2019-15647 | High 8.8 | Before 1.3.5 | Fixed in 1.3.5 | 27 Aug 2019 |
Read the published descriptions
- CVE-2026-104385, 6 Oct 2026
- Unauthenticated Sensitive Data Exposure in Groundhogg <= 4.8.3 versions. CVE record
- CVE-2026-104408, 5 Oct 2026
- Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Groundhogg Groundhogg groundhogg allows Blind SQL Injection.This issue affects Groundhogg: from n/a through 4.8.3. CVE record
- CVE-2026-97644, 3 Oct 2026
- The Groundhogg - CRM, Newsletters, and Marketing Automation plugin for WordPress is vulnerable to Privilege Escalation via Contact Identity Rebinding in all versions up to, and including, 4.9 The vulnerability exists because the `create_contact` function in the v3 REST endpoint (`POST /gh/v3/contacts`) is gated solely by the `add_contacts` capability and forwards the full request payload - including the security-bearing `user_id` column - into the upsert path of `Contacts_DB::add()`, which bypasses the ownership guard that `Contacts_DB::update()` enforces, allowing an attacker to rebind any existing contact record to an arbitrary WordPress user ID. This makes it possible for authenticated attackers with Sales Representative-level access and above to upsert their own contact row to point to an Administrator's user ID, then invoke the v4 email-test endpoint (`POST /gh/v4/emails/test`) - also accessible to the Sales Representative role via the `send_emails` capability - to generate an `{auto_login_url}` one-time permissions key bound to the rebound contact, and consume that link to call `wp_set_auth_cookie()` and gain a fully authenticated session as the WordPress Administrator. CVE record
- CVE-2026-81741, 9 Sep 2026
- The Groundhogg - CRM, Newsletters, and Marketing Automation WordPress plugin before 4.7.2 does not restrict the redirect target of its email preference confirmation flow to the site's own host, allowing unauthenticated attackers to redirect visitors to an arbitrary external URL by way of a crafted link. CVE record
- CVE-2026-81660, 30 Aug 2026
- The Groundhogg - CRM, Newsletters, and Marketing Automation WordPress plugin before 4.5.13 does not validate or escape values submitted to some optional web form fields before storing them and outputting them back in an administrative area, allowing unauthenticated users to perform Stored Cross-Site Scripting attacks against high privilege users. CVE record
- CVE-2026-18387, 15 Aug 2026
- The Groundhogg - CRM, Newsletters, and Marketing Automation plugin for WordPress is vulnerable to generic SQL Injection via the 'tag_query' parameter in all versions up to, and including, 4.5.14 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with vendor-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. Exploitation requires the attacker to trigger the vulnerable Legacy_Contact_Query code path by submitting an unknown filter type (e.g. filters[0][0][type]=force_fallback), which causes a FilterException that dispatches execution away from the modern query handler. CVE record
- CVE-2026-11454, 5 Aug 2026
- The Groundhogg - CRM, Newsletters, and Marketing Automation plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 4.5.2 via the GET /wp-json/gh/v4/contacts/<id> REST endpoint. The endpoint's permission callback checks only the role-level view_contacts capability and read_single() returns the full contact record by sequential integer ID without the object-level view_contact ownership check applied elsewhere in the codebase. This makes it possible for authenticated attackers holding view_contacts but not view_others_contacts - notably Groundhogg's built-in Sales Rep role, designed to see only its own contacts - to read any contact record on the site, including PII, contact meta, owner IDs, the admin edit URL, and (for contacts linked to a WordPress user) that user's full capability set. CVE record
- CVE-2026-14029, 2 Jul 2026
- The Groundhogg - CRM, Newsletters, and Marketing Automation plugin for WordPress is vulnerable to generic SQL Injection via the 'select' parameter in all versions up to, and including, 4.5.8 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with custom-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. Exploitation requires the attacker to hold a Groundhogg custom role with the view_contacts capability, which is granted by default to several built-in Groundhogg roles above the base subscriber level. CVE record
- CVE-2026-13331, 27 Jun 2026
- The Groundhogg - CRM, Newsletters, and Marketing Automation plugin for WordPress is vulnerable to generic SQL Injection via the 'search' parameter in all versions up to, and including, 4.5.5 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with marketer-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. CVE record
- CVE-2026-13333, 27 Jun 2026
- The Groundhogg - CRM, Newsletters, and Marketing Automation plugin for WordPress is vulnerable to generic SQL Injection via 'query[select]' Parameter in all versions up to, and including, 4.5.5 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Sales Representative-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. The sanitized Contact_Query code path can be bypassed by supplying an invalid filter type (e.g., query[filters][0][0][type]=invalid_filter_nonexistent), causing a FilterException to be caught and execution to fall through to the unsanitized Legacy_Contact_Query path. CVE record
- CVE-2026-13226, 26 Jun 2026
- The Groundhogg - CRM, Newsletters, and Marketing Automation plugin for WordPress is vulnerable to generic SQL Injection via the 'after' parameter in all versions up to, and including, 4.5.4 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Sales Manager-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. The AJAX handler wp_ajax_groundhogg_get_contacts_table has its capability check commented out and performs no nonce verification, meaning any authenticated user regardless of role can reach the vulnerable code path. CVE record
- CVE-2025-12750, 21 Nov 2025
- The Groundhogg - CRM, Newsletters, and Marketing Automation plugin for WordPress is vulnerable to SQL Injection via the 'term' parameter in all versions up to, and including, 4.2.6.1 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Administrator-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. CVE record
- CVE-2025-4206, 9 May 2025
- The WordPress CRM, Email & Marketing Automation for WordPress | Award Winner - Groundhogg plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the 'process_export_delete' and 'process_import_delete' functions in all versions up to, and including, 4.1.1.2. This makes it possible for authenticated attackers, with Administrator-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). CVE record
- CVE-2025-1267, 1 Apr 2025
- The Groundhogg plugin for Wordpress is vulnerable to Stored Cross-Site Scripting via the ‘label' parameter in versions up to, and including, 3.7.4.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Administrator-level access, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This only affects multi-site installations and installations where unfiltered_html has been disabled. CVE record
- CVE-2025-0394, 14 Jan 2025
- The WordPress CRM, Email & Marketing Automation for WordPress | Award Winner - Groundhogg plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the gh_big_file_upload() function in all versions up to, and including, 3.7.3.5. This makes it possible for authenticated attackers, with Author-level access and above, to upload arbitrary files on the affected site's server which may make remote code execution possible. CVE record
- CVE-2023-2715, 20 May 2023
- The Groundhogg plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'submit_ticket' function in versions up to, and including, 2.7.9.8. This makes it possible for authenticated attackers to create a support ticket that sends the website's data to the plugin developer, and it is also possible to create an admin access with an auto login link that is also sent to the plugin developer with the ticket. It only works if the plugin is activated with a valid license. CVE record
- CVE-2023-2716, 20 May 2023
- The Groundhogg plugin for WordPress is vulnerable to unauthorized access of data and modification of data due to a missing capability check on the 'ajax_upload_file' function in versions up to, and including, 2.7.9.8. This makes it possible for authenticated attackers, with subscriber-level access and above, to upload a file to the contact, and then lists all the other uploaded files related to the contact. CVE record
- CVE-2023-2717, 20 May 2023
- 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. CVE record
- CVE-2023-2735, 20 May 2023
- The Groundhogg plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'gh_form' shortcode in versions up to, and including, 2.7.9.8 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers with contributor-level and above permissions to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Please note this only works with legacy contact forms. CVE record
- CVE-2023-2736, 20 May 2023
- 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 in the 'ajax_edit_contact' function. This makes it possible for authenticated attackers to receive the auto login link via shortcode and then modify the assigned user to the auto login link to elevate verified user privileges via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. CVE record
- CVE-2023-2714, 20 May 2023
- The Groundhogg plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'check_license' functions in versions up to, and including, 2.7.9.8. This makes it possible for authenticated attackers, with subscriber-level permissions and above, to change the license key and support license key, but it can only be changed to a valid license key. CVE record
- CVE-2023-1425, 10 Apr 2023
- The WordPress CRM, Email & Marketing Automation for WordPress | Award Winner - Groundhogg WordPress plugin before 2.7.9.4 does not properly sanitise and escape a parameter before using it in a SQL statement, leading to a SQL injection exploitable by high privilege users such as admins CVE record
- CVE-2019-15647, 27 Aug 2019
- The groundhogg plugin before 1.3.5 for WordPress has wp-admin/admin-ajax.php?action=bulk_action_listener remote code execution. CVE record
What to do if you run Groundhogg
If you run Groundhogg, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Groundhogg vulnerabilities
Free. We email you when a new vulnerability is published for Groundhogg, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.