dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-57389

HIGH · 8.6 CVSS v3.1 Published 2026-07-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 5 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
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Adrian Tobey Groundhogg groundhogg allows Path Traversal.This issue affects Groundhogg: from n/a through <= 4.4.1.

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

Path traversal vulnerability in Groundhogg WordPress plugin versions <= 4.4.1 allows attackers to access files outside restricted directories using directory traversal sequences (e.g., ../). This improper input validation enables unauthorized file system access.

MitigationUpdate Groundhogg plugin to a patched version beyond 4.4.1. As an interim measure, implement web server-level restrictions and disable directory listing to limit exposure.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/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. Confirm Groundhogg plugin is installed
    Check for the Groundhogg plugin directory in WordPress (typically wp-content/plugins/groundhogg/). In WP-CLI, run: wp plugin list --name=groundhogg --format=table
    Affected if Groundhogg plugin is present in the WordPress installation
  2. Check installed Groundhogg version
    Read the plugin version from the main plugin file header (groundhogg/groundhogg.php), or query via WP-CLI: wp plugin get groundhogg --field=version
    Affected if Installed version is 4.4.1 or lower (any version up to and including 4.4.1)
  3. Identify if file-related features are active
    Examine the Groundhogg plugin for active file import/export, backup, or attachment handling modules. Check plugin settings page for any enabled file processing features
    Affected if File handling features (import, export, attachments) are enabled and processing user-supplied paths
  4. Inspect file operation code paths
    Review plugin source code for functions that accept file paths as input (file_get_contents, readfile, include, require). Check if these accept unvalidated user parameters
    Affected if Code paths accept path parameters without input validation or path sanitization

You are affected if Groundhogg plugin version 4.4.1 or lower is installed AND file handling features that accept path input are enabled in your configuration.

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 Groundhogg plugin to a patched version beyond 4.4.1. As an interim measure, implement web server-level restrictions and disable directory listing to limit exposure.

Recommended fix Moderate confidence

Groundhogg plugin version > 4.4.1 (check WordPress plugin repository or vendor for exact latest secure release)

  1. Backup your WordPress site and database before performing any updates
  2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
  3. Locate the Groundhogg plugin
  4. Check if an update is available - the vendor has released a fix for this vulnerability in a version after 4.4.1
  5. Update Groundhogg to the latest available version that contains the security fix
  6. Verify the update was successful and test critical functionality
Caveat Check plugin changelog for any breaking changes before upgrading, as minor/minor version updates may include functionality changes

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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 locally
dbcve dependency scanner

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