dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-14029

MEDIUM · 6.5 CVSS v3.1 Published 2026-07-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click 7 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Groundhogg WordPress plugin is vulnerable to SQL injection via the 'select' parameter in versions up to 4.5.8. The vulnerability results from insufficient input sanitization and lack of prepared SQL statements, allowing authenticated attackers with custom roles containing the view_contacts capability to inject arbitrary SQL queries and extract sensitive database information.

MitigationUpdate the Groundhogg plugin to a version beyond 4.5.8 which contains the security patch. Until then, restrict or revoke the view_contacts capability from untrusted custom roles.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Groundhogg plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Groundhogg' in the list. Note the version number displayed.
    Affected if Groundhogg plugin is present in the WordPress installation.
  2. Confirm the installed version
    Compare the installed Groundhogg version against the affected range (4.5.8 and below). The version is shown in the plugins list.
    Affected if The installed version is 4.5.8 or lower.
  3. Identify custom roles with view_contacts capability
    Use a role management plugin or query the WordPress database (wp_options table for roles) to list all roles. For each role, check if it includes the 'view_contacts' capability. In WP CLI: wp role list --fields=name,capabilities | grep view_contacts
    Affected if Any custom role (not built-in roles like Administrator, Editor, etc.) contains the view_contacts capability.
  4. Check user assignments to custom roles with view_contacts
    Query wp_usermeta for users with meta_key containing the custom role name, or use: wp user list --role=role_name for each custom role identified.
    Affected if There are users assigned to custom roles that include the view_contacts capability, especially users who are not fully trusted administrators.

A user is affected if Groundhogg plugin version is 4.5.8 or lower AND there exist custom roles with the view_contacts capability assigned to non-administrator users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Groundhogg plugin to a version beyond 4.5.8 which contains the security patch. Until then, restrict or revoke the view_contacts capability from untrusted custom roles.

Recommended fix Moderate confidence

A version newer than 4.5.8 (check wordpress.org/plugins/groundhogg/ for the latest stable release)

  1. 1. Identify the currently installed Groundhogg plugin version in WordPress admin under Plugins > Installed Plugins
  2. 2. Navigate to the official WordPress plugin repository at https://wordpress.org/plugins/groundhogg/ to check for a newer version
  3. 3. If a version newer than 4.5.8 is available, update the plugin through WordPress admin or via wp-cli: wp plugin update groundhogg
  4. 4. Verify the update was successful and test that the view_contacts functionality still works properly
  5. 5. Confirm the fix by reviewing the plugin changelog for mention of SQL injection security remediation
Caveat Minor: Review any changes to contact management functionality after upgrade, though no major breaking changes are typically introduced in security patches

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-14029 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-14029 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data