Contact Form by WD – responsive drag & drop contact form builder tool <= 1.7.18 - Authorization Bypass

2014-11-09 00:00
Kacper Szurek

Strategic Overview

Status
Patched in 1.7.19
Affected Version
<= 1.7.18
CVSS
8.1High
Weakness type
CWE-862 · Missing Authorization
CVE
CVE pending
View all Contact Form by WD – responsive drag & drop contact form builder tool vulnerabilities

At a glance

This record tracks a high-severity Missing Authorization vulnerability in the Contact Form by WD WordPress plugin, affecting versions <= 1.7.18. It carries a CVSS score of 8.1 (reachable over the network; low attack complexity; high integrity, availability impact). The issue is fixed in version 1.7.19; sites on affected versions should update now. Disclosed November 2014, reported by Kacper Szurek.

Vulnerability Overview

The Contact Form by WD – responsive drag & drop contact form builder tool plugin for WordPress is vulnerable to authorization bypass due to a missing capability check on the form_maker_cfm function in versions up to, and including, 1.7.18. This makes it possible for authenticated attackers, with subscriber-level permissions and above, to edit forms, including entering stored cross-site scripting, as output is not properly escaped.

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 interaction from a victim user. A successful exploit has high impact on integrity, availability.

CWE-862: Missing Authorization

Reaching this weakness in Contact Form by WD <= 1.7.18 takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Contact Form by WD the fix is 1.7.19: builds <= 1.7.18 are affected, anything from 1.7.19 onward is not.

Remediation

Update to version 1.7.19, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Contact Form by WD 1.7.19 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

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