dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-10862

HIGH · 7.5 CVSS v3.1 Published 2025-10-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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 SQL Injection in all versions up to, and including, 2.1.3. This is due to insufficient escaping on the 'id' 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.

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 WordPress popup builder plugin fails to properly sanitize the 'id' parameter before using it in an SQL query. Because the parameter is not escaped and the existing query lacks prepared statement preparation, an unauthenticated attacker can inject arbitrary SQL commands via the id parameter to exfiltrate data from the database.

MitigationUpdate the plugin to version 2.1.4 or later which contains the patched code. If no update is available, disable the plugin immediately. The fix requires using $wpdb->prepare() with proper placeholder substitution and validating the id parameter as a numeric integer.

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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. Locate the popup builder plugin
    In WordPress admin, go to Plugins > Installed Plugins and find the popup builder plugin. Note the version number displayed there. Alternatively, check the plugin's main PHP file header for the Version field.
    Affected if The installed version is unknown, or the version is below 2.1.4 (the fixed version).
  2. Verify the vulnerable code exists
    Access the plugin files via file manager or FTP. Open the main plugin file (usually named something like popup-builder.php or similar) and search for SQL queries that use the 'id' parameter without $wpdb->prepare(). Look for direct variable insertion like $wpdb->query("SELECT... WHERE id = " . $_GET['id']).
    Affected if The plugin file contains SQL queries using the 'id' parameter that lack $wpdb->prepare() and proper sanitization.
  3. Check plugin version in code
    If the admin version display is unavailable, open the plugin's main PHP file and locate the 'Version:' header comment. Compare this version number to 2.1.4.
    Affected if The version in the plugin header is below 2.1.4, indicating the unpatched version.
  4. Identify vulnerable endpoint
    The vulnerability affects any front-end or admin AJAX endpoint that processes the 'id' parameter. Test accessing common plugin endpoints (like /wp-admin/admin-ajax.php?action=popup_builder_get&id=1) or review plugin code for handlers that accept 'id' via $_GET or $_POST.
    Affected if The plugin processes 'id' parameter requests and the version is below 2.1.4.

The environment is affected if the WordPress popup builder plugin is installed with a version below 2.1.4 and the plugin processes the 'id' parameter in SQL queries without prepared statements.

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.1.4 or later which contains the patched code. If no update is available, disable the plugin immediately. The fix requires using $wpdb->prepare() with proper placeholder substitution and validating the id parameter as a numeric integer.

Recommended fix Moderate confidence

Version 2.1.4 or later of the Popup builder with Gamification, Multi-Step Popups, Page-Level Targeting, and WooCommerce Triggers plugin

  1. Check your WordPress site for the installed version of the 'Popup builder with Gamification, Multi-Step Popups, Page-Level Targeting, and WooCommerce Triggers' plugin
  2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
  3. Locate the plugin and verify the current version number
  4. Update the plugin to the latest available version (2.1.4 or later) which contains the security fix for the SQL Injection vulnerability
  5. After updating, verify the plugin is running the patched version

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-10862 — 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-10862 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