CVE-2026-104385

Groundhogg — CRM, Newsletters, and Marketing Automation <= 4.8.3 - Unauthenticated Information Exposure

2026-10-05 11:24
Ayukiab

Strategic Overview

Status
Patched in 4.9
Affected Plugin
Groundhogg — CRM, Newsletters, and Marketing Automation
Affected Version
<= 4.8.3
CVSS
5.3Medium
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2026-104385
View all Groundhogg — CRM, Newsletters, and Marketing Automation vulnerabilities

At a glance

CVE-2026-104385 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Groundhogg WordPress plugin, affecting versions <= 4.8.3. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 4.9; sites on affected versions should update now. Disclosed October 2026, reported by Ayukiab.

Vulnerability Overview

The Groundhogg — CRM, Newsletters, and Marketing Automation plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 4.8.3. This makes it possible for unauthenticated attackers to extract sensitive user or configuration data.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

Reaching this weakness in Groundhogg <= 4.8.3 takes no account at all. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For Groundhogg the fix is 4.9: builds <= 4.8.3 are affected, anything from 4.9 onward is not.

Remediation

Update to version 4.9, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Groundhogg 4.9 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-104385https://www.wordfence.com/threat-intel/vulnerabilities/id/f01a7f01-5a53-465c-a570-db242ffad6d5https://nvd.nist.gov/vuln/detail/CVE-2026-104385

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C