dbcve.org
GroundhoggWordPress extension

CVE-2024-37264

MEDIUM · 6.1 CVSS v3.1 Published 2024-07-22
Fix available
A fix is available. Upgrade to 3.4.3 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Groundhogg Inc. Groundhogg allows Reflected XSS.This issue affects Groundhogg: from n/a through 3.4.2.3.

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 · moderate confidence

Reflected XSS vulnerability in Groundhogg WordPress plugin versions through 3.4.2.3. User-supplied input is not properly neutralized before being returned in web page content, allowing attackers to inject malicious scripts via crafted URLs that execute in victim browsers.

MitigationUpgrade to version 3.4.2.4 or later. If immediate patching is not possible, implement web application firewall rules to detect and block XSS payloads in query parameters.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GroundhoggWordPress extension
Affected:< 3.4.3

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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. Check if Groundhogg plugin is installed
    Log into WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'Groundhogg' in the list. Alternatively, access your site via FTP or file manager and check /wp-content/plugins/ for a folder named 'groundhogg'.
    Affected if The Groundhogg plugin folder exists in the WordPress plugins directory.
  2. Identify the installed Groundhogg version
    In WordPress admin, find Groundhogg in the plugin list and read the version number displayed below the plugin name. Or, open the main plugin file (usually groundhogg/groundhogg.php) via file manager/FTP and look for the 'Version' header in the plugin comments at the top of the file.
    Affected if A version number is displayed or found in the plugin file header.
  3. Compare your version to the affected range
    Take the version number you found (for example, 3.4.2.3) and compare it numerically to 3.4.3. The affected range is any version less than 3.4.3, including all 3.4.2.x versions.
    Affected if The installed version is 3.4.2.3, 3.4.2.2, 3.4.2.1, 3.4.2, or any other version below 3.4.3.
  4. Verify the specific vulnerable endpoint (optional)
    If you have access to your web server logs or can test safely, examine URL parameters in requests to Groundhogg pages. Reflected XSS typically appears in query parameters. Check pages under /wp-admin/admin.php?page=gh_ or front-end pages using Groundhogg shortcodes.
    Affected if User-supplied parameters from the URL are reflected back into the page HTML without proper encoding.

You are affected if the Groundhogg WordPress plugin is installed and the version number is less than 3.4.3.

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
Upgrade available Upgrade to 3.4.3 or later
Fixed in 3.4.3
Interim mitigation

Upgrade to version 3.4.2.4 or later. If immediate patching is not possible, implement web application firewall rules to detect and block XSS payloads in query parameters.

Recommended fix High confidence

3.4.3

  1. 1. Backup your WordPress site and database before performing any updates
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
  3. 3. Find Groundhogg in the plugin list and click 'Update Now' if an update is available, or manually upload version 3.4.3
  4. 4. Alternatively, download Groundhogg 3.4.3 from the WordPress.org repository or your Groundhogg account
  5. 5. After updating, verify the version number shows 3.4.3 or higher
  6. 6. Test critical workflows and forms to ensure functionality remains intact

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

Fix this in Groundhogg 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 the upgrade done

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-2024-37264 — 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-2024-37264 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