dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-12997

HIGH · 7.5 CVSS v3.1 Published 2026-07-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
The Gravity Forms plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 2.10.4 via the 'gform_uploaded_files' parameter parameter. This makes it possible for unauthenticated attackers to read the contents of arbitrary files on the server, which can contain sensitive information. Exploitation requires the targeted form to not enforce login (so publicly accessible), which allows the unauthenticated attacker to reach the process_send_resume_link endpoint and supply an arbitrary recipient email address to receive the traversal-retrieved file as a notification attachment.

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 Gravity Forms WordPress plugin (versions up to 2.10.4) contains a directory traversal vulnerability in the 'gform_uploaded_files' parameter. Unauthenticated attackers can read arbitrary files on the server by exploiting the process_send_resume_link endpoint, provided the targeted form allows public access without login enforcement. The retrieved file is delivered as an attachment to an attacker-specified email address.

MitigationUpgrade to Gravity Forms version 2.10.5 or later. As an interim measure, ensure all forms have login enforcement enabled to prevent unauthenticated access to the vulnerable endpoint.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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. Confirm Gravity Forms plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for Gravity Forms, or check the wp-content/plugins directory for a gravityforms folder
    Affected if Gravity Forms plugin is not present on the WordPress site
  2. Identify the installed Gravity Forms version
    In WordPress admin, go to Forms > About, or check the version constant in /wp-content/plugins/gravityforms/version.php
    Affected if Version is 2.10.4 or lower (any version up to and including 2.10.4)
  3. Check for forms with public access enabled
    In WordPress admin, go to Forms > Settings > [select each form] > Settings tab and verify the "Require Login" option. Check if any form has this disabled, allowing anonymous access
    Affected if At least one form has "Require Login" disabled or unset, making the form publicly accessible

The environment is affected if Gravity Forms version 2.10.4 or lower is installed AND at least one form allows public access without login enforcement, exposing the vulnerable process_send_resume_link endpoint to unauthenticated attackers.

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 Gravity Forms version 2.10.5 or later. As an interim measure, ensure all forms have login enforcement enabled to prevent unauthenticated access to the vulnerable endpoint.

Recommended fix Moderate confidence

Upgrade to the latest version of Gravity Forms (currently available release) which addresses this vulnerability

  1. 1. Identify the current version of the Gravity Forms plugin installed on your WordPress site.
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard.
  3. 3. Locate Gravity Forms in the plugin list and check the version number.
  4. 4. If the installed version is 2.10.4 or lower, update to the latest available version of Gravity Forms.
  5. 5. Go to Forms > Settings and ensure that any publicly accessible forms have the "Require Login" option enabled under the form's settings to prevent unauthenticated exploitation.
  6. 6. After updating, verify the plugin version reflects the latest release.
  7. 7. Test that forms function correctly after the update, particularly any forms using file upload and notification features.
Caveat Review any custom integrations or hooks that may be affected by the plugin update, as minor version updates occasionally introduce behavior changes

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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