dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-13192

HIGH · 8.2 CVSS v3.1 Published 2026-02-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Popup Builder plugin for WordPress contains a SQL injection vulnerability in multiple REST API endpoints. Attackers can inject malicious SQL queries due to insufficient input sanitization and lack of prepared statements, allowing unauthenticated extraction of sensitive database information.

MitigationUpdate the plugin to version 2.2.3 or later to apply the full patch. If immediate updating is not possible, consider temporarily restricting REST API access or deploying a WAF rule to block SQL injection attempts.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if the plugin is installed
    In WordPress admin dashboard, go to Plugins > Installed Plugins and look for 'Popup builder with Gamification' or check the wp-content/plugins directory for a folder containing 'popup-builder' and 'gamification' in the name
    Affected if The plugin is present in the WordPress installation
  2. Check the installed plugin version
    In WordPress admin, click on the plugin name/details to view version information, or inspect the main plugin PHP file for the 'Version' header in the plugin comment block
    Affected if The installed version is lower than 2.2.3 (the patched version)
  3. Verify REST API endpoints are accessible
    Send a GET request to wp-json/wp/v2/ and enumerate endpoints related to the plugin (common paths include /popup-builder/ or similar REST routes). Use: curl -s https://yourdomain.com/wp-json/ | grep -i popup
    Affected if REST API endpoints for the plugin are publicly accessible without authentication
  4. Check for suspicious SQL injection patterns in access logs
    Review web server access logs (Apache/Nginx) for requests to REST API endpoints containing SQL operators like UNION, SELECT, OR 1=1, or unusual characters in parameters. Example: grep -E "(UNION|SELECT|OR 1=1|--)" /var/log/apache2/access.log
    Affected if Log entries show SQL injection attempts targeting popup-builder REST endpoints

A user is affected if the Popup builder with Gamification plugin is installed with a version lower than 2.2.3 and its REST API endpoints are publicly accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 2.2.3 or later to apply the full patch. If immediate updating is not possible, consider temporarily restricting REST API access or deploying a WAF rule to block SQL injection attempts.

Recommended fix High confidence

Plugin version 2.2.3

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the 'Popup builder with Gamification, Multi-Step Popups, Page-Level Targeting, and WooCommerce Triggers' plugin
  4. Click 'Update now' to upgrade to version 2.2.3
  5. Verify the update completed successfully by checking the plugin version

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-13192 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-13192 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data