CVE-2019-14695

Popup Builder <= 3.44 - SQL Injection

2019-08-06 00:00
Tin Duong

Strategic Overview

Status
Patched in 3.45
Affected Version
<= 3.44
CVSS
9.8Critical
Weakness type
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVE
CVE-2019-14695
View all Popup Builder – Create highly converting, mobile friendly marketing popups. vulnerabilities

At a glance

CVE-2019-14695 is a critical-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the Popup Builder WordPress plugin, affecting versions <= 3.44. 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 3.45; sites on affected versions should update now. Disclosed August 2019, reported by Tin Duong.

Vulnerability Overview

A SQL injection vulnerability exists in the Sygnoos Popup Builder plugin before 3.45 for WordPress. Successful exploitation of this vulnerability would allow a remote attacker to execute arbitrary SQL commands on the affected system via com/libs/Table.php because Subscribers Table ordering is mishandled.

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 Popup Builder <= 3.44 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 Popup Builder the fix is 3.45: builds <= 3.44 are affected, anything from 3.45 onward is not.

Remediation

Update to version 3.45, or a newer patched version

How does WordSec protect against this?

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