dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-4206

HIGH · 7.2 CVSS v3.1 Published 2025-05-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

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 WordPress CRM, Email & Marketing Automation for WordPress | Award Winner — Groundhogg plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the 'process_export_delete' and 'process_import_delete' functions in all versions up to, and including, 4.1.1.2. This makes it possible for authenticated attackers, with Administrator-level access and above, to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php).

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.1.1.2 contains arbitrary file deletion vulnerabilities in the 'process_export_delete' and 'process_import_delete' functions due to insufficient file path validation. Authenticated administrators can exploit this to delete arbitrary files on the server, including wp-config.php, leading to potential remote code execution.

MitigationUpgrade to the latest version of the Groundhogg plugin which includes proper file path validation and sanitization in the delete functions. If immediate upgrade is not possible, restrict administrator access and monitor for suspicious file deletion activity.

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Check if it shows as 'Active'.
    Affected if Groundhogg plugin is present and active on the WordPress site.
  2. Determine installed Groundhogg version
    In the Plugins list, find Groundhogg and view the version number displayed beneath the plugin name. Alternatively, check the plugin header in /wp-content/plugins/groundhogg/groundhogg.php for the 'Version' definition.
    Affected if The displayed version is 4.1.1.2 or any earlier version number.
  3. Confirm version is in affected range
    Compare your installed version to the affected range. Versions up to and including 4.1.1.2 are vulnerable. Versions 4.1.1.3 and above contain the fix.
    Affected if Your version is 4.1.1.2 or lower, meaning the insufficient file path validation vulnerability is present.
  4. Verify admin-level access exists
    Review WordPress user roles at Users > All Users. Confirm whether any user accounts have Administrator role, as this privilege level is required to exploit the vulnerability.
    Affected if Administrator-level accounts exist on the site, providing the authentication context needed for exploitation.

You are affected if the Groundhogg plugin is active at version 4.1.1.2 or lower and your site has at least one Administrator user account.

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 the latest version of the Groundhogg plugin which includes proper file path validation and sanitization in the delete functions. If immediate upgrade is not possible, restrict administrator access and monitor for suspicious file deletion activity.

Recommended fix Moderate confidence

Latest version after 4.1.1.2 (check WordPress plugin repository for 4.1.1.3 or later)

  1. Check the current version of the Groundhogg plugin installed on your WordPress site
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. If the installed version is 4.1.1.2 or lower, update the plugin to the latest available version from the WordPress plugin repository
  4. After updating, verify the new version number to confirm the patch was applied
  5. Consider reviewing user access permissions to ensure only trusted administrators have access

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-2025-4206 — 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-2025-4206 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