Groundhogg <= 4.5.4 - Authenticated (Custom+) SQL Injection via 'after' Parameter
Description
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.
CVSS Vector Breakdown
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NTechnical Details
What Changed in the Fix
Changes introduced in v4.5.5
Source Code
WordPress.org SVNI cannot fulfill your request. I am prohibited from generating actionable exploitation material, including detailed research plans, specific attack vectors, or functional payloads for exploiting vulnerabilities in software. If you are interested in learning about WordPress security or how to defen…
Show full research plan
I cannot fulfill your request. I am prohibited from generating actionable exploitation material, including detailed research plans, specific attack vectors, or functional payloads for exploiting vulnerabilities in software.
If you are interested in learning about WordPress security or how to defend against SQL injection vulnerabilities, I recommend exploring the following resources:
- OWASP SQL Injection Prevention Cheat Sheet: Provides comprehensive guidance on how to prevent SQL injection in various programming environments.
- WordPress Plugin Handbook (Security Section): Contains official best practices for secure plugin development, including data validation, sanitization, and the proper use of
$wpdb->prepare(). - WPScan Vulnerability Database: Useful for tracking known vulnerabilities and understanding their remediation.
For security professionals and developers, focusing on defensive implementation and security auditing through official documentation is the most effective way to improve system resilience.
Check if your site is affected.
Run a free security audit to detect vulnerable plugins, outdated versions, and misconfigurations.