Executive Summary

The vulnerability in the Popup builder with Gamification, Multi-Step Popups, Page-Level Targeting, and WooCommerce Triggers WordPress plugin is a generic SQL Injection affecting multiple REST API endpoints in all versions up to and including 2.2.0.

It occurs because user-supplied parameters are not properly escaped or prepared in SQL queries, allowing unauthenticated attackers to append additional SQL commands to existing queries.

This can be exploited to extract sensitive information from the database.

The vulnerability was partially patched in version 2.2.1 for unauthenticated users and fully patched in version 2.2.3 for users with Administrator or higher privileges.

Useful 0 Not Useful 0

Impact Analysis

This SQL Injection vulnerability can allow unauthenticated attackers to extract sensitive information from your WordPress site's database by injecting malicious SQL queries through the plugin's REST API endpoints.

Potential impacts include unauthorized access to confidential data such as subscriber information, campaign logs, and other stored data managed by the plugin.

Because the vulnerability affects unauthenticated users, attackers do not need valid credentials to exploit it, increasing the risk.

This could lead to data breaches, loss of user trust, and potential further exploitation of the compromised system.

Useful 0 Not Useful 0

Compliance Impact

I don't know

Useful 0 Not Useful 0

Detection Guidance

[{'type': 'paragraph', 'content': 'The vulnerability involves unauthenticated SQL Injection via multiple REST API endpoints in the Popup Builder Block WordPress plugin up to version 2.2.0. Detection can focus on monitoring and testing these REST API endpoints for suspicious SQL injection payloads.'}, {'type': 'paragraph', 'content': 'Specifically, the vulnerable endpoints include subscriber-related routes (GET, DELETE /subscribers) and popup-related routes (GET, POST, PUT, DELETE /popup/logs) that do not have sufficient permission checks or input sanitization.'}, {'type': 'paragraph', 'content': 'To detect exploitation attempts or the presence of the vulnerable plugin version, you can:'}, {'type': 'list_item', 'content': 'Check HTTP access logs for unusual or malformed requests to REST API endpoints such as `/wp-json/popup-builder-block/v1/subscribers` or `/wp-json/popup-builder-block/v1/popup/logs`.'}, {'type': 'list_item', 'content': 'Use curl or similar tools to test the REST API endpoints with crafted SQL injection payloads in parameters like `campaign_id`, `start`, `end`, or `id` to see if the server responds with database errors or unexpected data.'}, {'type': 'list_item', 'content': 'Example curl command to test GET subscribers endpoint for SQL injection:'}, {'type': 'list_item', 'content': "curl -X GET 'https://yourwordpresssite.com/wp-json/popup-builder-block/v1/subscribers?campaign_id=1%27%20OR%20%271%27=%271'"}, {'type': 'list_item', 'content': 'Example curl command to test GET popup logs endpoint:'}, {'type': 'list_item', 'content': "curl -X GET 'https://yourwordpresssite.com/wp-json/popup-builder-block/v1/popup/logs?campaignId=1&startDate=2026-01-01&endDate=2026-01-31&type=devices'"}, {'type': 'list_item', 'content': 'Monitor for SQL error messages or abnormal responses indicating injection.'}, {'type': 'paragraph', 'content': 'Additionally, scanning the WordPress installation to identify the plugin version (<= 2.2.0) can help detect vulnerable systems.'}] [3, 4]

Useful 0 Not Useful 0

Mitigation Strategies

The primary mitigation step is to update the Popup Builder Block WordPress plugin to a patched version.

• Upgrade the plugin to version 2.2.1 or later to patch unauthenticated SQL Injection for general users.
• For full mitigation including Administrator+ level user protections, upgrade to version 2.2.3 or later.
• If immediate upgrade is not possible, restrict access to the vulnerable REST API endpoints by:
• Implementing firewall or web application firewall (WAF) rules to block suspicious requests targeting `/wp-json/popup-builder-block/v1/subscribers` and `/wp-json/popup-builder-block/v1/popup/*` endpoints.
• Limiting access to the WordPress REST API to authenticated users or trusted IP addresses.
• Review and harden permissions on REST API endpoints, especially those lacking nonce or permission checks (GET and DELETE subscriber routes).

Additionally, monitor logs for exploitation attempts and consider temporarily disabling the plugin if exploitation is suspected.

Useful 0 Not Useful 0