WordPress security changelog
MEDIUM CVE-2026-11454 Deferred

Groundhogg Sales Reps can read every CRM contact through REST

Groundhogg through 4.5.2 protects GET /wp-json/gh/v4/contacts/ only with the broad view_contacts capability. read_single() accepts a sequential contact ID without applying the object-level view_contact ownership check used elsewhere. A user with view_contacts but not view_others_contacts, notably the built-in Sales Rep role, can enumerate every contact and retrieve PII, contact metadata, owner IDs, administrator edit URLs and linked WordPress users' capability sets.

CVE / CNA score 6.5 CVSS 3.1 · security@wordfence.com
NVD score Pending NVD has not published its own CVSS assessment.
Component
Groundhogg — CRM, Newsletters, and Marketing Automation
Plugin slug
groundhogg
Affected
<= 4.5.2
Safe version
4.5.3
Published
Aug 05, 2026
Weakness
CWE-639 — Authorization Bypass Through User-Controlled Key

This CVE was published Aug 05, 2026 and is one of 30 known issues for this plugin.

What to do

Update, patch or deactivate.

Update Groundhogg to 4.5.3 or later. The linked upstream comparison identifies 4.5.3 as the fixed release. Audit Sales Rep accounts and contact REST access and assess exposed contact data according to the site's privacy obligations.

A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Source record

Technical description

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 / CNA vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

References

Primary and upstream sources