Horizon Alert
Summary of the vulnerability and why it matters
A critical vulnerability exists in the Popup Builder WordPress plugin, allowing unauthenticated attackers to delete all published popups on a site with a single request. This issue stems from the plugin's failure to properly verify user authorization for certain actions.
- Unauthenticated attackers can trash all published popups.
- Critical flaw impacts a widely used WordPress marketing tool.
- Confirm relevance and exposure of this marketing plugin.
Attack Path
How an attacker could exploit the issue
An unauthenticated attacker can bypass authorization checks in the Popup Builder WordPress plugin to delete all published popups. This is achieved by sending a specific GET request that exploits a flaw in how the plugin handles popup previews, causing it to mistakenly target all popups for deletion.
- No login required to attack.
- Triggered by a crafted GET request.
- Can delete all published popups.
Live Threat
Current exploitation, exposure, and threat context
When supported by the advisory, this vulnerability could allow unauthenticated attackers to remove all published marketing popups from a WordPress site. This is possible because the plugin may not properly check if a user is authorized to perform certain actions, potentially leading to widespread disruption of website content.
- All published popups at risk.
- Unauthenticated GET request exposes the flaw.
- Disrupts website content delivery.
Operational Fix
Recommended remediation, mitigation, and detection steps
The WordPress plugin, Popup Builder, is vulnerable to an authorization bypass that allows unauthenticated attackers to delete all published popups. This critical vulnerability, affecting all versions up to and including 4.4.5, requires immediate attention. Website owners and administrators should prioritize identifying all instances of this plugin, verifying its reachability and business criticality, and coordinating with the application owner to plan remediation.
- WordPress site owners/administrators should own this issue.
- Verify plugin instances and exposure to public networks.
- Plan immediate vendor-coordinated remediation or mitigation.