CVE-2026-5109
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 Stored Cross-Site Scripting in versions up to and including 2.10.0. This is due to insufficient validation and output escaping of Product Option field values. The vulnerability exists because the state validation function accepts submitted values where the wp_kses()-sanitized version matches a legitimate option value, but then stores the raw unsanitized value in the database. When administrators view entry details via the Order Summary section, the option_label is output directly without escaping (view-order-summary.php line 32), executing the injected JavaScript. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in entry data that will execute whenever an administrator accesses the entry details 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 stores unsanitized Product Option field values in the database while validating input by comparing a wp_kses()-sanitized version against legitimate values. When administrators view entry details via the Order Summary section, the option_label is rendered without output escaping (view-order-summary.php line 32), allowing stored XSS execution.
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.
-
Confirm Gravity Forms plugin is installedAccess WordPress admin panel, navigate to Plugins > Installed Plugins, and locate Gravity Forms in the list. Alternatively, check the file system at wp-content/plugins/gravityforms/ for the presence of the plugin directory.Affected if Gravity Forms plugin is not found in the WordPress installation
-
Identify installed Gravity Forms versionIn WordPress admin, go to Forms > Settings. The version number is typically displayed at the bottom of the settings page. Alternatively, check the main plugin file header at wp-content/plugins/gravityforms/gravityforms.php for the Version comment.Affected if The installed version is unknown or falls within any vulnerable version range where unsanitized Product Option values are stored and rendered without escaping
-
Verify access to entry details via Order SummaryLog in as an administrator, navigate to Forms > Entries, select any entry, and locate the Order Summary section on the entry detail page. Confirm that view-order-summary.php is being loaded when the entry is viewed.Affected if The Order Summary section is accessible and displays entry data without additional security controls
-
Inspect for Product Option field usage in formsIn WordPress admin, go to Forms > Forms, edit any form containing product-related fields, and check if Product Option fields (such as dropdown options or checkboxes) are configured. These fields store values that could be unsanitized in the database.Affected if Forms contain Product Option fields with user-supplied option values that may have been saved without proper sanitization
A user is affected if Gravity Forms is installed with any version that stores Product Option values without sanitization and renders them without output escaping in the Order Summary section accessible to 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 the latest version of Gravity Forms which properly escapes output and validates/stores sanitized input values. As a temporary measure, restrict access to entry details pages or implement additional output escaping at the application layer.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5109 — 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-5109 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