CVE-2026-5113
Stored XSS in Gravity Forms WordPress Plugin
Publication date: 2026-05-02
Last updated on: 2026-05-05
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| gravity_forms | gravity_forms | to 2.10.0 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The Gravity Forms plugin for WordPress has a Stored Cross-Site Scripting (XSS) vulnerability in versions up to and including 2.10.0. This occurs because of a flawed state validation mechanism involving consent field hidden inputs. The validation creates two hashes: one from the raw input and one from the sanitized input using wp_kses(). It only fails validation if both hashes do not match the original state. Attackers can inject malicious scripts using tags that wp_kses() strips (like <svg>), causing the sanitized hash to match while the malicious raw input is saved in the database. When an administrator views the Entries List page, the malicious script executes because the stored consent label is output without proper escaping.
How can this vulnerability impact me? :
This vulnerability allows unauthenticated attackers to inject arbitrary web scripts into Gravity Forms entries. These scripts execute whenever an authenticated administrator views the Entries List page, potentially leading to unauthorized actions, data theft, or compromise of the administrator's session. This can result in loss of control over the WordPress site, data breaches, or further exploitation.
What immediate steps should I take to mitigate this vulnerability?
The vulnerability affects Gravity Forms plugin versions up to and including 2.10.0. Immediate mitigation involves updating the Gravity Forms plugin to a version later than 2.10.0 where this vulnerability is fixed.
Since the vulnerability allows unauthenticated attackers to inject stored XSS payloads via consent field hidden inputs, restricting access to the Entries List page to trusted administrators and monitoring for suspicious entries can help reduce risk until the plugin is updated.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability in Gravity Forms allows unauthenticated attackers to inject stored cross-site scripting (XSS) payloads that execute when an authenticated administrator views the entries list page. This can lead to unauthorized script execution within the administrative interface.
Such a vulnerability could potentially impact compliance with standards and regulations like GDPR and HIPAA because it may lead to unauthorized access or manipulation of sensitive data stored within the form entries. XSS attacks can be used to steal session tokens, manipulate data, or perform actions on behalf of administrators, thereby compromising data integrity and confidentiality.
However, the provided context and resources do not explicitly discuss the direct impact of this vulnerability on compliance with GDPR, HIPAA, or other common standards.