dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-13333

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-27
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 8 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 'query[select]' Parameter in all versions up to, and including, 4.5.5 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 Sales Representative-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. The sanitized Contact_Query code path can be bypassed by supplying an invalid filter type (e.g., query[filters][0][0][type]=invalid_filter_nonexistent), causing a FilterException to be caught and execution to fall through to the unsanitized Legacy_Contact_Query path.

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 fails to properly sanitize the 'query[select]' parameter in its CRM query functionality. An authenticated attacker with Sales Representative-level access can bypass the sanitized Contact_Query code path by supplying an invalid filter type, causing a FilterException that routes execution to an unsanitized Legacy_Contact_Query path. This allows arbitrary SQL injection to extract sensitive database information.

MitigationUpgrade to Groundhogg plugin version 4.5.6 or later which contains the fix. Until patched, limit user permissions to below Sales Representative-level access.

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. Identify if Groundhogg plugin is installed
    Check the WordPress plugins directory for the Groundhogg plugin folder, or query the wp_options table for an option containing 'groundhogg' in the active_plugins list.
    Affected if Groundhogg plugin is present in the WordPress installation
  2. Determine the installed Groundhogg plugin version
    Read the main plugin file header (usually groundhogg/groundhogg.php) to extract the 'Version:' field, or query wp_options for a version-related option name.
    Affected if The version is lower than 4.5.6 (vulnerable versions)
  3. Verify if the vulnerable CRM query endpoint is accessible
    Check if the WordPress REST API endpoint /wp-json/groundhogg/v4/contacts/ or the admin ajax action 'gh_get_contacts' is available and responds to authenticated requests.
    Affected if The CRM contact query functionality is active and reachable
  4. Check for user accounts with Sales Representative role or higher
    Query the wp_usermeta table for users with meta_key 'wp_capabilities' containing 'groundhogg_sales_rep' or 'administrator', or use get_users() with role parameter in WordPress.
    Affected if At least one user account has Sales Representative-level permissions or higher
  5. Inspect request parameters for the vulnerable query[select] pattern
    If logs are available, review access logs or WordPress debug logs for requests containing 'query[select]' parameter that may indicate exploitation attempts.
    Affected if Suspicious query[select] parameter values appear in web server or application logs

Your environment is affected if the Groundhogg plugin version is below 4.5.6 AND the CRM query functionality is accessible to users with Sales Representative-level permissions or higher.

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

Upgrade to Groundhogg plugin version 4.5.6 or later which contains the fix. Until patched, limit user permissions to below Sales Representative-level access.

Recommended fix Moderate confidence

version greater than 4.5.6 (confirm latest version from wordpress.org)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the Groundhogg plugin
  4. Check if an update is available and update to the latest version
  5. Verify the update completes successfully

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-13333 — 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-13333 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