dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-40727

HIGH · 7.7 CVSS v3.1 Published 2026-06-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
83/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
Sales Representative Arbitrary File Deletion in Groundhogg <= 4.4 versions.

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

An authenticated arbitrary file deletion vulnerability in the Groundhogg WordPress plugin versions 4.4 and below allows users with Sales Representative privileges to delete arbitrary files on the server, potentially causing data loss or service disruption.

MitigationUpgrade the Groundhogg plugin to a version newer than 4.4 and review file permissions on the server to limit the impact of arbitrary file operations.

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Verify Groundhogg plugin is installed
    Navigate to WordPress admin > Plugins and check if Groundhogg plugin appears in the installed plugins list
    Affected if Groundhogg plugin is present in the WordPress installation
  2. Check installed Groundhogg version
    In WordPress admin > Plugins > Installed Plugins, find Groundhogg and read the version number from the plugin description; or check the version in the main plugin file header (groundhogg.php)
    Affected if Version is 4.4 or lower (any version 4.4.x or below)
  3. Confirm Sales Representative role exists
    Go to WordPress admin > Users > Roles, or use a role management plugin or wp-cli command 'wp role list' to verify if the Sales Representative role is present
    Affected if The Sales Representative role exists in the WordPress user role system
  4. Identify users with Sales Representative access
    In WordPress admin > Users, filter or check which users are assigned the Sales Representative role; or use query: SELECT user_id, meta_value FROM wp_usermeta WHERE meta_key = 'wp_capabilities' AND meta_value LIKE '%sales_rep%'
    Affected if Any user account has Sales Representative privileges assigned

If Groundhogg plugin version 4.4 or lower is installed AND the Sales Representative role exists with at least one user assigned, the environment is affected by this vulnerability.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade the Groundhogg plugin to a version newer than 4.4 and review file permissions on the server to limit the impact of arbitrary file operations.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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