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

CVE-2026-3492

MEDIUM · 6.4 CVSS v3.1 Published 2026-03-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable 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 all versions up to, and including, 2.9.28.1. This is due to a compound failure involving missing authorization on the `create_from_template` AJAX endpoint (allowing any authenticated user to create forms), insufficient input sanitization (`sanitize_text_field()` preserves single quotes), and missing output escaping when the form title is rendered in the Form Switcher dropdown (`title` attribute constructed without `esc_attr()`, and JavaScript `saferHtml` utility only escapes `&`, `<`, `>` but not quotes). This makes it possible for authenticated attackers, with Subscriber-level access and above, to inject arbitrary JavaScript that executes when an Administrator searches in the Form Switcher dropdown in the Form Editor.

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 has a stored XSS vulnerability in versions up to 2.9.28.1 caused by a combination of three flaws: the `create_from_template` AJAX endpoint lacks authorization checks allowing any authenticated user to create forms, `sanitize_text_field()` does not remove single quotes from input, and the Form Switcher dropdown renders form titles without proper escaping (missing `esc_attr()` on the title attribute and the JavaScript saferHtml utility only escaping `&`, `<`, `>` but not quotes). This allows authenticated attackers with Subscriber-level access to inject malicious JavaScript that executes when an Administrator uses the Form Switcher.

MitigationUpdate to the patched version of Gravity Forms (2.9.29 or later) and ensure all form titles are properly sanitized and escaped before rendering in any admin interface context.

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
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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. Identify Gravity Forms version
    Check the installed Gravity Forms plugin version in WordPress admin under Plugins > Installed Plugins, or read the main plugin file header for the Version field
    Affected if Version is 2.9.28.1 or lower
  2. Verify Form Switcher feature exists
    Navigate to the Gravity Forms admin interface and look for the Form Switcher dropdown menu, typically found in the admin toolbar or form list view
    Affected if Form Switcher dropdown is present and accessible in the admin interface
  3. Confirm user role configuration
    Review WordPress user roles at Users > All Users and check if any accounts have Subscriber role or higher permissions
    Affected if At least one user account with Subscriber role or higher exists on the site
  4. Test AJAX endpoint accessibility
    Inspect network requests or check if the gf_create_from_template AJAX action is registered and accessible to authenticated users via /wp-admin/admin-ajax.php
    Affected if The create_from_template AJAX endpoint accepts requests from any authenticated user without authorization checks

Your environment is affected if Gravity Forms version is 2.9.28.1 or lower, the Form Switcher dropdown feature is enabled, and the site has at least one authenticated user with Subscriber-level access who can access the vulnerable AJAX endpoint.

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 the patched version of Gravity Forms (2.9.29 or later) and ensure all form titles are properly sanitized and escaped before rendering in any admin interface context.

Recommended fix Moderate confidence

Gravity Forms version 2.9.29 or later

  1. 1. Update the Gravity Forms plugin to version 2.9.29 or later to address the stored XSS vulnerability.
  2. 2. After updating, verify that the Form Switcher dropdown functionality works correctly.
  3. 3. Consider reviewing user roles and permissions to ensure only trusted users have form creation access.

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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