dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2024-12157

HIGH · 7.5 CVSS v3.1 Published 2025-01-07
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 – MailChimp, GetResponse and ActiveCampaign Intergrations plugin for WordPress is vulnerable to SQL Injection via the 'id' parameter of the 'upc_delete_db_record' AJAX action in all versions up to, and including, 3.2.6 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.

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 plugin for WordPress contains a SQL injection vulnerability in the 'upc_delete_db_record' AJAX action. The 'id' parameter is not properly escaped before being used in a SQL query, and the query lacks prepare() statements, allowing unauthenticated attackers to inject arbitrary SQL commands and extract sensitive database information.

MitigationUpdate the plugin to version 3.2.7 or later, which includes proper input sanitization and uses WordPress $wpdb->prepare() for the SQL query.

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. Verify Popup plugin is installed
    Log into WordPress admin and navigate to Plugins > Installed Plugins, or check the /wp-content/plugins/ directory for a folder named 'popup' or similar.
    Affected if The Popup plugin is present in the WordPress installation
  2. Check installed plugin version
    In WordPress admin, find the Popup plugin in the plugins list and note the version number displayed, or inspect the main plugin PHP file for a 'Version' header comment.
    Affected if Version is lower than 3.2.7 (the fixed release)
  3. Identify the vulnerable AJAX endpoint
    Locate the plugin PHP files and search for the function handling 'upc_delete_db_record' AJAX action, typically registered with add_action('wp_ajax_upc_delete_db_record'...) or wp_ajax_nopriv_...
    Affected if The 'upc_delete_db_record' AJAX action exists and is registered without authentication protection (wp_ajax_nopriv)
  4. Inspect the SQL query code
    Examine the function handling the AJAX call and look for the SQL query using the 'id' parameter without $wpdb->prepare() and without sanitize_text_field() or intval() on the input.
    Affected if The code uses $_POST['id'] or similar directly in a SQL query without prepare() or proper escaping

A user is affected if the Popup plugin is installed with a version lower than 3.2.7 and the plugin code contains the unprotected 'upc_delete_db_record' AJAX action with unsanitized 'id' parameter in a SQL query.

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 3.2.7 or later, which includes proper input sanitization and uses WordPress $wpdb->prepare() for the SQL query.

Recommended fix High confidence

Version 3.2.7 or latest available version

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Find 'Popup – MailChimp, GetResponse and ActiveCampaign Integrations'
  4. Click 'Update now' if an update is available, or manually download the latest version from wordpress.org and upload it
  5. Verify the updated version is 3.2.7 or higher

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-2024-12157 — 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-2024-12157 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