dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-13226

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-26
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 the 'after' parameter in all versions up to, and including, 4.5.4 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 Manager-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 AJAX handler wp_ajax_groundhogg_get_contacts_table has its capability check commented out and performs no nonce verification, meaning any authenticated user regardless of role can reach the vulnerable code 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 versions up to 4.5.4 contain a SQL Injection vulnerability in the AJAX handler wp_ajax_groundhogg_get_contacts_table. The 'after' parameter is not escaped or prepared in the SQL query, allowing authenticated attackers to inject arbitrary SQL. Additionally, the capability check is commented out and no nonce verification exists, meaning any authenticated user (regardless of role) can reach and exploit this flaw.

MitigationUpdate to version 4.5.5 or later which includes proper SQL query preparation using $wpdb->prepare() and restores capability checks with nonce verification. Until then, disable the plugin or restrict user authentication as a temporary workaround.

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 or look for /wp-content/plugins/groundhogg/ folder. In WordPress admin, go to Plugins > Installed Plugins and look for Groundhogg.
    Affected if Groundhogg plugin is present in the WordPress installation
  2. Determine installed plugin version
    In WordPress admin > Plugins > Installed Plugins, find Groundhogg and read the version number displayed. Alternatively, check the main plugin file header in /wp-content/plugins/groundhogg/groundhogg.php for the Version field.
    Affected if Version is 4.5.4 or lower (any version up to and including 4.5.4)
  3. Verify any authenticated users exist
    In WordPress admin > Users, check if any user accounts exist. Even low-privilege users (subscriber, customer, etc.) can exploit this flaw.
    Affected if At least one user account exists in the WordPress installation
  4. Check if AJAX endpoint responds
    Send a POST request to /wp-admin/admin-ajax.php with action=groundhogg_get_contacts_table and any value for the 'after' parameter. No nonce or capability is required. Example: curl -X POST http://target/wp-admin/admin-ajax.php -d 'action=groundhogg_get_contacts_table&after=1'
    Affected if The AJAX handler returns a response (even an error) indicating the endpoint is active and reachable

You are affected if the Groundhogg plugin versions 4.5.4 or lower is installed, any authenticated user account exists in WordPress, and the groundhogg_get_contacts_table AJAX endpoint is accessible without authentication or capability checks.

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 to version 4.5.5 or later which includes proper SQL query preparation using $wpdb->prepare() and restores capability checks with nonce verification. Until then, disable the plugin or restrict user authentication as a temporary workaround.

Recommended fix Moderate confidence

Any version released after 4.5.4 (e.g., 4.5.5 or later)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the Groundhogg plugin
  4. Check the current version installed (should be 4.5.4 or below)
  5. If an update is available, click 'Update Now' to update to the latest version
  6. Alternatively, download the latest version of Groundhogg from the WordPress plugin repository and manually upload via Plugins > Add New > Upload Plugin
  7. After updating, verify the version number reflects a release after 4.5.4
Caveat Review the plugin changelog for any breaking changes between your current version and the updated version before upgrading in production environments

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-13226 — 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-13226 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