Google Forms < 0.92 - Unauthenticated Server Side Request Forgery
Strategic Overview
- Status
- Patched in 0.92
- Affected Plugin
- Google Forms
- Affected Version
< 0.92- CVSS
- 7.2High
- Weakness type
- CWE-918 · Server-Side Request Forgery (SSRF)
- CVE
CVE pending
At a glance
This record tracks a high-severity Server-Side Request Forgery (SSRF) vulnerability in the Google Forms WordPress plugin, affecting versions < 0.92. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 0.92; sites on affected versions should update now. Disclosed January 2018, reported by Klikki Oy.
Vulnerability Overview
The Google Forms plugin for WordPress is vulnerable to Server Side Request Forgery in versions before 0.92. This allowed Unauthenticated attackers to proxy requests through the plugin to an attacker-controlled host, which could also lead to a reflected Cross-Site Scripting scenario.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-918: Server-Side Request Forgery (SSRF)
Reaching this weakness in Google Forms < 0.92 takes no account at all. Server-side request forgery means the application fetches a URL supplied by the caller, turning the server into a proxy for requests the attacker could not make directly.
The request originates from inside the hosting network, which is how these flaws reach cloud metadata endpoints, internal admin panels and services that trust local traffic. For Google Forms the fix is 0.92: builds < 0.92 are affected, anything from 0.92 onward is not.
Remediation
Update to version 0.92, or a newer patched version
How does WordSec protect against this?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Google Forms 0.92 closes this, and updating the plugin is the step that ends it.
- Firewall
- Login Security
- Alerts
External References
Related records
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C