dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-5111

HIGH · 7.2 CVSS v3.1 Published 2026-05-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable No privileges 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 Gravity Forms plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to and including 2.10.0. This is due to insufficient input validation and output escaping on Hidden Product field values when used inside Repeater fields, where repeater subfields bypass state validation checks and the Hidden Product validate() method only validates the quantity field while ignoring the product name field that is later output without proper escaping in the get_value_entry_detail() method. This makes it possible for unauthenticated attackers to inject arbitrary web scripts through form submissions that will execute whenever an administrator views the entry details.

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 plugin up to v2.10.0 contains a stored XSS vulnerability in Hidden Product fields used within Repeater fields. The validate() method only checks the quantity field while ignoring the product name field, and get_value_entry_detail() outputs this value without escaping, allowing unauthenticated attackers to inject malicious scripts via form submissions.

MitigationUpdate to a version beyond 2.10.0 where the vendor has addressed input validation and output escaping for Hidden Product fields in repeater contexts. Until then, restrict form creation/management to trusted users and consider disabling repeater fields with Hidden Product fields.

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
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/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. Check Gravity Forms version
    Locate the Gravity Forms plugin file (typically in /wp-content/plugins/gravityforms/ or via WordPress admin > Plugins) and check the version number in the plugin header or changelog
    Affected if Version is 2.10.0 or lower (versions after 2.10.0 contain the fix)
  2. Identify forms using Repeater fields
    Review all forms in the Gravity Forms admin panel and check if any form contains a Repeater field (field type: Repeater)
    Affected if At least one form contains a Repeater field
  3. Check for Hidden Product fields inside Repeaters
    For each form with a Repeater field, inspect the Repeater's field list to determine if it contains a Hidden Product field (field type: Product > Hidden)
    Affected if A Hidden Product field exists within a Repeater field in any form
  4. Verify unauthenticated form submission is allowed
    Check the form settings > Restrictions tab to see if the form accepts submissions from unauthenticated users (Require Login is unchecked)
    Affected if Form with Hidden Product in Repeater allows anonymous submissions
  5. Inspect recent form entries for suspicious content
    Review Gravity Forms > Entries for forms with Hidden Product fields in Repeaters; examine the entry detail values in the product name field for unescaped HTML/script tags
    Affected if Entry values in Hidden Product fields contain unescaped HTML or script content

Environment is affected if Gravity Forms version is 2.10.0 or lower AND any form contains a Hidden Product field within a Repeater field that accepts unauthenticated submissions.

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 to a version beyond 2.10.0 where the vendor has addressed input validation and output escaping for Hidden Product fields in repeater contexts. Until then, restrict form creation/management to trusted users and consider disabling repeater fields with Hidden Product fields.

Recommended fix Moderate confidence

A version newer than 2.10.0 (specific fixed release available from Gravity Forms)

  1. 1. Backup your WordPress site and database before making any changes.
  2. 2. Navigate to the Plugins section in WordPress admin dashboard.
  3. 3. Locate the Gravity Forms plugin and check the current version installed.
  4. 4. If the installed version is 2.10.0 or earlier, update the plugin to the latest available version.
  5. 5. After updating, verify the plugin version has changed to confirm the update was successful.
  6. 6. Test form submissions with Hidden Product fields inside Repeater fields to ensure functionality remains intact.
  7. 7. Review entry details for any submissions to confirm the XSS vulnerability is remediated.

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-2026-5111 — 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-5111 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