Groundhogg <= 4.5.4 - Authenticated (Custom+) SQL Injection via 'after' Parameter
Strategic Overview
- Status
- Patched in 4.5.5
- Affected Plugin
- Groundhogg — CRM, Newsletters, and Marketing Automation
- Affected Version
<= 4.5.4- CVSS
- 6.5Medium
- Weakness type
- CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
- CVE
CVE-2026-13226
At a glance
CVE-2026-13226 is a medium-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the Groundhogg WordPress plugin, affecting versions <= 4.5.4. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires an authenticated account at Custom level or above. The issue is fixed in version 4.5.5; sites on affected versions should update now. Disclosed June 2026, reported by Wordfence PRISM.
Vulnerability Overview
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.
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 confidentiality.
CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Groundhogg <= 4.5.4 carries this weakness at after, and reaching it takes an account at Custom level or above. SQL injection happens when request data is concatenated into a query instead of being bound as a parameter, letting an attacker change the structure of the statement rather than just its values.
A working injection can read any table the database user can see, which on a WordPress install means user records, password hashes and session or API secrets stored in options. For Groundhogg the fix is 4.5.5: builds <= 4.5.4 are affected, anything from 4.5.5 onward is not.
Remediation
Update to version 4.5.5, or a newer patched version
How does WordSec protect against this?
An attacker needs Custom 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.5.5 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.8CVE-2019-15647: WordPress CRM RCE
CVE-2019-15647 - 8.1CVE-2026-57389: Groundhogg Arbitrary File Deletion
CVE-2026-57389 - 8.1CVE-2026-40727: Groundhogg Arbitrary File Deletion
CVE-2026-40727 - 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-2025-4206: WordPress CRM Arbitrary File Deletion
CVE-2025-4206
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C