CVE-2026-11454 MEDIUM

CVE-2026-11454: Groundhogg — CRM, Newsletters, and Marketing Automation <= 4.5.2 - Insecure Direct Object Reference

Vendor Trainingbusinesspros
Product Groundhogg — CRM, Newsletters, and Marketing Automation
Weakness CWE-639 · IDOR
Published August 5, 2026
Last update August 5, 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 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.

Explanation of Vulnerability in Simple Terms

02Summary

Groundhogg versions up to 4.5.2 contain an authorization bypass vulnerability in how user-controlled keys are validated. An attacker with low-level access can read sensitive data from other users' records by manipulating request parameters. The vulnerability does not allow data modification or system unavailability.

What an attacker can do

03Attacker Capabilities

Read sensitive data from other users' CRM records and contact information.

Potential impact on your site

04Site Impact

User data privacy is compromised; contacts and customer information may be exposed to unauthorized site users.

Conditions required to exploit

05Prerequisites

Attacker must have a low-level user account on the site; no user interaction required.

Key dates

06Disclosure timeline

August 5, 2026 CVE published
August 5, 2026 Record updated

Related vulnerabilities

08Related CVE