CVE-2025-13192 HIGH

CVE-2025-13192: Popup builder with Gamification <= 2.2.0 - Unauthenticated SQL Injection via Multiple REST API Endpoints

Vendor Roxnor
Product Popup builder with Gamification, Multi-Step Popups, Page-Level Targeting, and WooCommerce Triggers
Weakness CWE-89 · SQLi
Published February 4, 2026
Last update April 8, 2026

CVSS base score

8.2/10
Attack vector Network
Attack complexity Low
Privileges required None
User interaction None
Confidentiality High
Integrity Low

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

What the vulnerability does

01Description

The Popup builder with Gamification, Multi-Step Popups, Page-Level Targeting, and WooCommerce Triggers plugin for WordPress is vulnerable to generic SQL Injection via the multiple REST API endpoints in all versions up to, and including, 2.2.0 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. Vulnerability was patched in version 2.2.1 for unauthenticated users, and fully patched in version 2.2.3 for Administrator+ level users.

Explanation of Vulnerability in Simple Terms

02Summary

The Popup Builder plugin contains a SQL injection vulnerability in versions up to 2.2.0. An unauthenticated attacker can send a specially crafted network request to extract sensitive data from the site's database, such as user credentials or configuration details. No user interaction is required. The vulnerability has a CVSS score of 8.2, indicating high severity.

What an attacker can do

03Attacker Capabilities

Extract sensitive data from the site database without authentication.

Potential impact on your site

04Site Impact

Attackers can read user data, credentials, and site configuration from your database.

Conditions required to exploit

05Prerequisites

Network access to the site; no authentication or user interaction required.

Key dates

06Disclosure timeline

February 4, 2026 CVE published
April 8, 2026 Record updated