CVE-2026-14029 MEDIUM

CVE-2026-14029: Groundhogg <= 4.5.8 - Authenticated (Custom+) SQL Injection via 'select' Parameter

Vendor Trainingbusinesspros
Product Groundhogg — CRM, Newsletters, and Marketing Automation
Weakness CWE-89 · SQLi
Published July 2, 2026
Last update July 2, 2026

CVSS base score

6.5/10
Attack vector Network
Attack complexity Low
Privileges required Low
User interaction None
Confidentiality High
Integrity None

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

What the vulnerability does

01Description

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.

Explanation of Vulnerability in Simple Terms

02Summary

Groundhogg versions up to 4.5.8 contain a SQL injection vulnerability in database query handling. An authenticated user with low privileges can craft malicious input to read sensitive data from the database, including user information and configuration details. The vulnerability requires valid login credentials but no additional user interaction.

What an attacker can do

03Attacker Capabilities

Read sensitive data from the site's database, including user records and configuration information.

Potential impact on your site

04Site Impact

User data and site configuration may be exposed to authenticated attackers; immediate patching required.

Conditions required to exploit

05Prerequisites

Attacker must have a valid user account with low-level privileges (e.g., subscriber or contributor role).

Key dates

06Disclosure timeline

July 2, 2026 CVE published

Related vulnerabilities

08Related CVE