Vulnerabilities

Vulnerability · CVE-2026-5109

The Gravity Forms plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to and including 2.10.0.

Published May 2, 2026 · catalog updated Jun 17, 2026 · The Gravity Forms plugin

Check if you run it

No confirmed exploitation is on record for CVE-2026-5109. EPSS is 0.30%. Act only if a listed version of The Gravity Forms plugin is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (The Gravity Forms plugin).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High7.2
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.30%
Remediation
Version ranges on file
Affected products
stated named in the record

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 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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • stated named in the record<= 2.10.0

How to fix CVE-2026-5109

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-5109. EPSS is 0.30%. Act only if a listed version of The Gravity Forms plugin is installed.

Which versions are affected?

Compare what you have installed with named in the record <= 2.10.0. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-79: Cross-site Scripting (XSS). EPSS 0.30%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. May 2, 2026 · NIST NVD

    Detected

    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 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

  2. Jun 17, 2026 · NIST NVD

    Updated

    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 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

Sources

  • CVE.orgVulnerability recordCVE-2026-5109

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-5109

    30-day exploitation probability 0.3%

    first.org
  • NIST NVDVulnerability recordCVE-2026-5109

    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 validation and output escaping of Product Option field values. The vulnerability exists because the state validation function ac

    nvd.nist.gov

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.