CVE-2020-9006

Popup Builder 2.2.8 - 2.6.7.6 - PHP Object Injection

2020-02-16 00:00
Zeroauth

Strategic Overview

Status
Patched in 3.0
Affected Plugin
Popup Builder – Create highly converting, mobile friendly marketing popups.
Affected Version
2.2.8 – 2.6.7.6
CVSS
9.8Critical
Weakness type
CWE-502 · Deserialization of Untrusted Data
CVE
CVE-2020-9006
View all Popup Builder – Create highly converting, mobile friendly marketing popups. vulnerabilities

At a glance

CVE-2020-9006 is a critical-severity Deserialization of Untrusted Data vulnerability in the Popup Builder WordPress plugin, affecting versions 2.2.8 – 2.6.7.6. 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.0; sites on affected versions should update now. Disclosed February 2020, reported by Zeroauth.

Vulnerability Overview

The Popup Builder plugin 2.2.8 through 2.6.7.6 for WordPress is vulnerable to SQL injection (in the sgImportPopups function in sg_popup_ajax.php) via PHP Deserialization on attacker-controlled data with the attachmentUrl POST variable. This allows creation of an arbitrary WordPress Administrator account, leading to possible Remote Code Execution because Administrators can run PHP code on Wordpress instances. (This issue has been fixed in the 3.x branch of popup-builder.)

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-502: Deserialization of Untrusted Data

Reaching this weakness in Popup Builder 2.2.8 – 2.6.7.6 takes a caller who can reach the endpoint. Deserialization of untrusted data means the application reconstructs objects from input a caller controls, letting the attacker choose which classes get instantiated and what their properties hold.

A workable chain turns deserialization into file writes, deletions or code execution, depending on what the loaded classes do in their magic methods. For Popup Builder the fix is 3.0: builds 2.2.8 – 2.6.7.6 are affected, anything from 3.0 onward is not.

Remediation

Update to version 3.0, 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. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: Popup Builder 3.0 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2020-9006https://www.wordfence.com/threat-intel/vulnerabilities/id/470fbac6-45bf-400e-b415-32e7989abbadhttps://nvd.nist.gov/vuln/detail/CVE-2020-9006

Related records

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