CVE-2026-5112
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 · uneditedThe Gravity Forms plugin for WordPress is vulnerable to Unauthenticated Stored Cross-Site Scripting in versions up to and including 2.10.0. This is due to insufficient input validation and output escaping of Calculation Product field product names when rendered inside Repeater fields. The validate() method in the GF_Field_Calculation class only validates the quantity field (.3) and completely ignores the product name field (.1), allowing malicious HTML to pass through validation. When the value is saved, the sanitize_entry_value() method returns the raw value without sanitization for fields where HTML is not expected. Subsequently, when an entry is viewed in wp-admin, the get_value_entry_detail() method concatenates the unescaped product name directly into the output string, which is then rendered by the repeater's get_value_entry_detail() method without further escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts via form submissions that will execute whenever an authenticated administrator with the gravityforms_view_entries capability accesses the entry detail page.
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 confidenceThe Gravity Forms plugin up to 2.10.0 contains an unauthenticated stored XSS vulnerability in the Calculation Product field within Repeater fields. The validate() method only validates the quantity field (.3) but ignores the product name field (.1), allowing malicious HTML to pass. The sanitize_entry_value() method then returns the raw unsanitized value, and get_value_entry_detail() concatenates this unescaped value directly into HTML output when viewed by administrators.
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 checksWork through these to decide whether this CVE applies to you.
-
Check Gravity Forms installed versionLook up the version number in your WordPress plugin directory under Plugins > Installed Plugins, or check the version constant in /wp-content/plugins/gravityforms/gravityforms.phpAffected if version is 2.10.0 or lower
-
Identify forms with Repeater fieldsIn Gravity Forms editor, look for fields with the Repeater field type added to any form. Check each form's fields list for the Repeater field button.Affected if any form contains a Repeater field
-
Identify Calculation Product fields inside RepeatersIn the Gravity Forms editor, expand each Repeater field and check if there is a Product field with Calculation enabled inside the repeater. Look for fields with type 'product' and calculation settings.Affected if a Calculation Product field exists inside a Repeater
-
Check for existing entries with malicious payload in product nameIn WordPress admin, go to Forms > Entries and view entries from forms with Calculation Product fields in repeaters. Check the entry detail view for any product name field values that contain unsanitized HTML script tags or event handlers.Affected if entries show unescaped HTML in product name fields when viewed
-
Verify entry detail rendering is accessibleNavigate to Forms > Entries > [Form] > [Entry] and inspect the page source. Look for the product name field value rendered between tags without HTML encoding.Affected if product name values render as raw HTML in entry details
You are affected if Gravity Forms version is 2.10.0 or lower AND you have forms using Calculation Product fields inside Repeater fields, with entries viewable by administrators.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade to Gravity Forms version 2.10.1 or later which implements proper input validation for product name fields and output escaping in the entry detail rendering. If immediate upgrade is not possible, restrict the gravityforms_view_entries capability to only highly trusted users.
- Consultation3.0 h
- Implementation5.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5112 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-5112 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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