Vulnerability in Groundhogg — CRM, Newsletters, and Marketing Automation (WordPress plugin) (CVE-2026-11454)
Summary
Vulnerability in Groundhogg — CRM, Newsletters, and Marketing Automation (WordPress plugin) (CVE-2026-11454). Confidential information can be exposed externally. Exploitable via GET /wp-json/gh/v4/contacts/.
Original description
The description as published by the source.
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/ 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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-11454 has been found in Groundhogg — CRM, Newsletters, and Marketing Automation (WordPress plugin).
Attackers can target a specific entry point like GET /wp-json/gh/v4/contacts/ over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.5/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Groundhogg — CRM, Newsletters, and Marketing Automation (WordPress plugin) CVE-2026-11454" on the vendor's site.
CVE-2026-11454 (Groundhogg — CRM, Newsletters, and Marketing Automation (WordPress plugin)) — CWE-639 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: GET /wp-json/gh/v4/contacts/
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-639) exists in Groundhogg — CRM, Newsletters, and Marketing Automation (WordPress plugin). Attackers reach the vulnerable code path via GET /wp-json/gh/v4/contacts/.
Check the vendor advisory for the affected versions of Groundhogg — CRM, Newsletters, and Marketing Automation (WordPress plugin). Attack surface: GET /wp-json/gh/v4/contacts/.
Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual GET /wp-json/gh/v4/contacts/ requests with malformed payloads or SQL meta-characters. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Groundhogg — CRM, Newsletters, and Marketing Automation (WordPress plugin) を使っているサービスとバージョンを洗い出す。
-
2Hunt for indicators of compromise detect
grep 'GET /wp-json/gh/v4/contacts/' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /wp-json/gh/v4/contacts/への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against GET /wp-json/gh/v4/contacts/ on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。