CVE-2018-20964

Contact Form Email <= 1.2.65 - Cross-Site Request Forgery

2019-08-12 00:00
Anonymous

Strategic Overview

Status
Patched in 1.2.66
Affected Plugin
Contact Form Email
Affected Version
<= 1.2.65
CVSS
8.8High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2018-20964
View all Contact Form Email vulnerabilities

At a glance

CVE-2018-20964 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the Contact Form Email WordPress plugin, affecting versions <= 1.2.65. 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.2.66; sites on affected versions should update now. Disclosed August 2019.

Vulnerability Overview

The contact-form-to-email plugin before 1.2.66 for WordPress has CSRF.

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 Email <= 1.2.65 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 Email the fix is 1.2.66: builds <= 1.2.65 are affected, anything from 1.2.66 onward is not.

Remediation

Update to version 1.2.66, or a newer patched version

How does WordSec protect against this?

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