dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-48866

CRITICAL · 9.6 CVSS v3.1 Published 2026-06-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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 Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Rocketgenius Inc. Gravity Forms allows Path Traversal. This issue affects Gravity Forms: from n/a through 2.10.0.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 Gravity Forms WordPress plugin allows attackers to access files outside restricted directories through manipulation of file path sequences (e.g., '../'). The critical CVSS 9.6 indicates severe impact, likely enabling unauthorized file read access.

MitigationUpdate to the latest patched version of Gravity Forms. If no patch available, implement WAF rules to block path traversal patterns and restrict file system access permissions on the web server.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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 Gravity Forms plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins, or check the plugin files in /wp-content/plugins/gravityforms/ for the version file
    Affected if Gravity Forms plugin is not present - not affected
  2. Determine installed Gravity Forms version
    Check the main plugin file header or version.php in /wp-content/plugins/gravityforms/ for the 'Version' attribute
    Affected if Version is 2.10.0.1 or lower - potentially affected by the path traversal flaw
  3. Confirm file upload functionality is in use
    Check Gravity Forms form settings for fields that enable file uploads (File Upload field type) or review active forms that accept file submissions
    Affected if File upload fields are configured - the path traversal could be exploited through these inputs
  4. Inspect web server logs for traversal attempts
    Search access logs for requests containing '../' or '..%2F' patterns targeting Gravity Forms upload endpoints, typically in /wp-content/plugins/gravityforms/
    Affected if Suspicious traversal patterns found in logs targeting Gravity Forms - potential exploitation detected

If Gravity Forms version is 2.10.0.1 or lower and file upload functionality is enabled, the environment is vulnerable to path traversal exploitation.

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

Update to the latest patched version of Gravity Forms. If no patch available, implement WAF rules to block path traversal patterns and restrict file system access permissions on the web server.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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