Gravity Forms <= 2.0.6.5 - Cross-Site Scripting

2016-09-07 00:00
c0mmand3rOpSec

Strategic Overview

Status
Patched in 2.0.7
Affected Plugin
Gravity Forms
Affected Version
<= 2.0.6.5
CVSS
5.4Medium
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE pending
View all Gravity Forms vulnerabilities

At a glance

This record tracks a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Gravity Forms WordPress plugin, affecting versions <= 2.0.6.5. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). The issue is fixed in version 2.0.7; sites on affected versions should update now. Disclosed September 2016, reported by c0mmand3rOpSec.

Vulnerability Overview

WordPress Plugin Gravity Forms is prone to a cross-site scripting vulnerability because it fails to properly sanitize user-supplied input. An attacker may leverage this issue to execute arbitrary script code in the browser of an unsuspecting user in the context of the affected site. This can allow the attacker to steal cookie-based authentication credentials and launch other attacks. WordPress Plugin Gravity Forms version 2.0.6.5 is vulnerable; prior versions may also be affected.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed.

CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Reaching this weakness in Gravity Forms <= 2.0.6.5 takes a caller who can reach the endpoint. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.

Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For Gravity Forms the fix is 2.0.7: builds <= 2.0.6.5 are affected, anything from 2.0.7 onward is not.

Remediation

Update to version 2.0.7, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Gravity Forms: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Gravity Forms 2.0.7 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/c89d56e2-68aa-4caf-bc1b-9aa32ec11ba3

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C