CVE-2019-13575

Contact Form, Drag and Drop Form Builder for WordPress – Everest Forms <= 1.4.9 - SQL Injection

2019-07-18 00:00
Tin Duong

Strategic Overview

Status
Patched in 1.5.0
Affected Version
< 1.5.0
CVSS
9.8Critical
Weakness type
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVE
CVE-2019-13575
View all Everest Forms – Contact Form, Payment Form, Quiz, Survey & Custom Form Builder with AI vulnerabilities

At a glance

CVE-2019-13575 is a critical-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the Everest Forms WordPress plugin, affecting versions < 1.5.0. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 1.5.0; sites on affected versions should update now. Disclosed July 2019, reported by Tin Duong.

Vulnerability Overview

A SQL injection vulnerability exists in WPEverest Everest Forms plugin for WordPress through 1.4.9. Successful exploitation of this vulnerability would allow a remote attacker to execute arbitrary SQL commands on the affected system via includes/evf-entry-functions.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, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Reaching this weakness in Everest Forms < 1.5.0 takes a caller who can reach the endpoint. SQL injection happens when request data is concatenated into a query instead of being bound as a parameter, letting an attacker change the structure of the statement rather than just its values.

A working injection can read any table the database user can see, which on a WordPress install means user records, password hashes and session or API secrets stored in options. For Everest Forms the fix is 1.5.0: builds < 1.5.0 are affected, anything from 1.5.0 onward is not.

Remediation

Update to version 1.5.0, or a newer patched version

How does WordSec protect against this?

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