CVE-2026-13331
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 · uneditedThe Groundhogg — CRM, Newsletters, and Marketing Automation plugin for WordPress is vulnerable to generic SQL Injection via the 'search' 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 marketer-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
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 confidenceThe Groundhogg WordPress plugin fails to properly escape the 'search' parameter and lacks prepared statements in its SQL queries, allowing authenticated users with marketer-level access to inject arbitrary SQL commands. This enables extraction of sensitive database contents through SQL injection.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Groundhogg plugin installation and versionNavigate to WordPress Admin > Plugins and locate Groundhogg, or inspect the plugin main file (wp-content/plugins/groundhogg/groundhogg.php) and look for the 'Version' header in the plugin commentsAffected if Groundhogg plugin is installed and version is lower than 4.5.6
-
Identify if marketer-level user role existsGo to WordPress Admin > Users > Roles, or query the wp_options table for 'groundhogg_roles' to see if the 'marketer' role is definedAffected if The 'marketer' role exists in the WordPress installation and is assigned to any user account
-
Verify users with marketer access existQuery the wp_usermeta table for meta_key='wp_capabilities' containing 'marketer', or check User list in WordPress admin for accounts with Marketer roleAffected if At least one user account has marketer-level privileges
-
Check if search functionality is accessible to marketer usersAttempt to access the Groundhogg contacts/people search feature while logged in as a marketer-level user, or inspect the plugin source for the search query handlerAffected if Marketer users can access and use the search/filter functionality in the plugin
The environment is affected if Groundhogg plugin version is below 4.5.6 AND at least one user with marketer-level access exists who can access the search functionality.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpdate to version 4.5.6 or later. If immediate update is not possible, disable the plugin or restrict user access to marketer-level accounts until the patch can be applied.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-13331 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-13331 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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