dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-12158

MEDIUM · 5.3 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 →
62/100
Remediation priority · Elevated
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 unauthorized loss of data due to a missing capability check on the 'upc_delete_db_data' AJAX action in all versions up to, and including, 3.2.6. This makes it possible for unauthenticated attackers to delete the DB data for the plugin.

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 – MailChimp, GetResponse and ActiveCampaign Integrations WordPress plugin has a broken access control vulnerability in its AJAX handler. The 'upc_delete_db_data' AJAX action lacks a capability check, allowing any unauthenticated user to trigger database deletion operations. This is an IDOR/broken access control issue with CVSS 5.3.

MitigationUpdate the plugin to version 3.2.7 or later which includes the missing capability check. If immediate updating is not feasible, consider disabling the plugin or implementing WAF rules to block the vulnerable AJAX endpoint until patching is possible.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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. Verify the Popup plugin is installed
    Check your WordPress plugins directory (wp-content/plugins) for folders containing 'popup' and 'mailchimp' or 'popup-by-popup', or list installed plugins via WP-CLI: wp plugin list --status=active --format=csv
    Affected if The plugin appears in the active plugins list
  2. Identify the installed plugin version
    Open the main plugin PHP file (usually popup.php, popup-by-popup.php, or similar in the plugin folder) and locate the 'Version:' header in the plugin comment block, or check the readme.txt file
    Affected if The version number is lower than 3.2.7 (the fixed version)
  3. Confirm the vulnerable AJAX endpoint exists
    Search the plugin source code for 'upc_delete_db_data' to verify this AJAX action handler exists, or test access by sending a POST request to /wp-admin/admin-ajax.php with action=upc_delete_db_data (no authentication required)
    Affected if The AJAX action responds or the code contains the vulnerable handler without a capability check (look for 'current_user_can' or 'manage_options' in that function)
  4. Check for database changes after potential exploitation
    Review your WordPress database tables, particularly any custom tables created by the plugin, for unexpected deletion or truncation; also check wp_posts/wp_postmeta for missing popup-related records
    Affected if Unexpected data loss is detected in plugin-related tables

You are affected if the Popup - MailChimp, GetResponse and ActiveCampaign Integrations plugin is installed with a version lower than 3.2.7 and the upc_delete_db_data AJAX action is accessible without authentication.

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 the missing capability check. If immediate updating is not feasible, consider disabling the plugin or implementing WAF rules to block the vulnerable AJAX endpoint until patching is possible.

Recommended fix Moderate confidence

Latest version available on WordPress.org (beyond 3.2.6)

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'The Popup – MailChimp, GetResponse and ActiveCampaign Integrations' plugin
  4. Check the current version number to confirm it is 3.2.6 or below
  5. Click 'Update now' if an update is available, or manually download the latest version from wordpress.org and upload via Plugins > Add New > Upload Plugin
  6. After updating, verify the new version number reflects an update beyond 3.2.6
  7. Test that the plugin functionality remains intact

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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