CVE-2015-4010

Encrypted Contact Form < 1.1 - Cross-Site Scripting

2015-06-08 00:00
Nitin Venkatesh

Strategic Overview

Status
Patched in 1.1
Affected Plugin
Encrypted Contact Form
Affected Version
< 1.1
CVSS
6.1Medium
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE-2015-4010
View all Encrypted Contact Form vulnerabilities

At a glance

CVE-2015-4010 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Encrypted Contact Form WordPress plugin, affecting versions < 1.1. It carries a CVSS score of 6.1 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.1; sites on affected versions should update now. Disclosed June 2015, reported by Nitin Venkatesh.

Vulnerability Overview

Cross-site request forgery (CSRF) vulnerability in the Encrypted Contact Form plugin before 1.1 for WordPress allows remote attackers to hijack the authentication of administrators for requests that conduct cross-site scripting (XSS) attacks via the iframe_url parameter in an Update Page action in the conformconf page to wp-admin/options-general.php.

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-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Reaching this weakness in Encrypted Contact Form < 1.1 takes a caller who can reach the endpoint. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.

Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For Encrypted Contact Form the fix is 1.1: builds < 1.1 are affected, anything from 1.1 onward is not.

Remediation

Update to version 1.1, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

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