CVE-2017-20053

Contact Form Manager <= 1.4.3 - Cross-Site Request Forgery

2017-03-01 00:00
Edwin Molenaar

Strategic Overview

Status
Patched in 1.4.4
Affected Plugin
Contact Form Manager
Affected Version
<= 1.4.3
CVSS
8.8High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2017-20053
View all Contact Form Manager vulnerabilities

At a glance

CVE-2017-20053 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the Contact Form Manager WordPress plugin, affecting versions <= 1.4.3. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 1.4.4; sites on affected versions should update now. Disclosed March 2017, reported by Edwin Molenaar.

Vulnerability Overview

A vulnerability was found in XYZScripts Contact Form Manager Plugin. It has been declared as problematic. Affected by this vulnerability is an unknown functionality. The manipulation leads to cross-site request forgery. The attack can be launched remotely. The exploit has been disclosed to the public and may be used.

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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

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

Reaching this weakness in Contact Form Manager <= 1.4.3 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 Manager the fix is 1.4.4: builds <= 1.4.3 are affected, anything from 1.4.4 onward is not.

Remediation

Update to version 1.4.4, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Contact Form Manager: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Contact Form Manager 1.4.4 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