# CVE-2026-5113: Gravity Forms <= 2.10.0 - Unauthenticated Stored Cross-Site Scripting via Consent Field Hidden Input

> Unauthenticated attackers can inject malicious scripts via consent fields that execute when administrators view entries, potentially leading to account takeover.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 May 2026
- **Updated:** 4 May 2026
- **Also known as:** GHSA-3rfw-27f2-r488

## What is CVE-2026-5113?

CVE-2026-5113 is a high-severity cross-site scripting vulnerability in Gravity Forms, published on 2 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Gravity Forms plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Consent field hidden inputs in versions up to and including 2.10.0. This is due to a flawed state validation mechanism that fails open when input is sanitized by wp_kses(), combined with insufficient output escaping. The state validation logic creates two hashes (raw input and wp_kses-sanitized input) and only fails validation if BOTH hashes don't match the original state. When an attacker injects XSS payloads using tags stripped by wp_kses() (like <svg>), the sanitized hash matches while the malicious raw value is preserved and saved to the database. When administrators view the Entries List page, the stored malicious consent label is retrieved and output without escaping, causing the XSS payload to execute. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in entries that will execute whenever an authenticated administrator accesses the entries list page.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-5113?


## How do I fix CVE-2026-5113?

No fix has been published for CVE-2026-5113 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-5113 being exploited?

There is no known exploitation of CVE-2026-5113 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-5113 and fix it if it is affected.

What it is: CVE-2026-5113 is a high-severity cross-site scripting vulnerability in Gravity Forms, published on 2 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-5113 in the wild and no public exploit code.

Affected product: Gravity Forms. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-5113/ (Markdown: https://insights.sbomify.com/CVE-2026-5113/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-5113
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-5113
- OSV: https://osv.dev/vulnerability/CVE-2026-5113

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-5113/
Summaries are generated and may contain mistakes; the official description above is the record.