CVE-2022-29495

Popup Builder – Create highly converting, mobile friendly marketing popups. <= 4.1.11 - Cross-Site Request Forgery to Settings Update

2022-06-30 00:00
Rafie Muhammad

Strategic Overview

Status
Patched in 4.1.12
Affected Plugin
Popup Builder – Create highly converting, mobile friendly marketing popups.
Affected Version
<= 4.1.11
CVSS
8.8High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2022-29495
View all Popup Builder – Create highly converting, mobile friendly marketing popups. vulnerabilities

At a glance

CVE-2022-29495 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the Popup Builder WordPress plugin, affecting versions <= 4.1.11. 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 4.1.12; sites on affected versions should update now. Disclosed June 2022, reported by Rafie Muhammad.

Vulnerability Overview

The "Popup Builder – Create highly converting, mobile friendly marketing popups." plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 4.1.11. This is due to missing or incorrect nonce validation on the saveSettings() function. This makes it possible for unauthenticated attackers to modify the plugin's settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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)

Popup Builder <= 4.1.11 carries this weakness at saveSettings(), and reaching it 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 Popup Builder the fix is 4.1.12: builds <= 4.1.11 are affected, anything from 4.1.12 onward is not.

Remediation

Update to version 4.1.12, 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 4.1.12 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2022-29495https://www.wordfence.com/threat-intel/vulnerabilities/id/fda10117-b562-496e-8a17-88ee350ce8f2https://nvd.nist.gov/vuln/detail/CVE-2022-29495

Related records

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