CVE-2015-6965

Contact Form Generator : Creative form builder for WordPress <= 2.1.86 - Cross-Site Request Forgery

2015-09-04 00:00
Joaquin Ramirez Martinez

Strategic Overview

Status
Patched in 2.5.0
Affected Version
<= 2.1.86
CVSS
6.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2015-6965
View all Contact Form Generator : Creative form builder for WordPress vulnerabilities

At a glance

CVE-2015-6965 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Contact Form Generator WordPress plugin, affecting versions <= 2.1.86. It carries a CVSS score of 6.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.5.0; sites on affected versions should update now. Disclosed September 2015, reported by Joaquin Ramirez Martinez.

Vulnerability Overview

The Contact Form Generator : Creative form builder for WordPress for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.1.86. This is due to missing or incorrect nonce validation on cfg_forms page. This makes it possible for unauthenticated attackers to modify and create contact form fields, create and delete forms, create and modify templates, and inject Cross-Site Scripting payloads via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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.

CWE-352: Cross-Site Request Forgery (CSRF)

Reaching this weakness in Contact Form Generator <= 2.1.86 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Contact Form Generator the fix is 2.5.0: builds <= 2.1.86 are affected, anything from 2.5.0 onward is not.

Remediation

Update to version 2.5.0, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

Related records

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