dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2024-12627

HIGH · 7.5 CVSS v3.1 Published 2025-01-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable 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 Coupon X: Discount Pop Up, Promo Code Pop Ups, Announcement Pop Up, WooCommerce Popups plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 1.3.5 via deserialization of untrusted input from post content passed to the capture_email AJAX action. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject a PHP Object. No known POP chain is present in the vulnerable software. If a POP chain is present via an additional plugin or theme installed on the target system, it could allow the attacker to delete arbitrary files, retrieve sensitive data, or execute code.

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 Coupon X WordPress plugin up to version 1.3.5 is vulnerable to PHP Object Injection via deserialization of untrusted post content in the capture_email AJAX action. Authenticated attackers with Contributor-level access or higher can inject arbitrary PHP objects. Although no POP chain exists in the plugin itself, the vulnerability could be exploited if other plugins or themes on the target system provide a POP chain.

MitigationUpdate the Coupon X plugin to version 1.3.6 or later to patch the deserialization vulnerability. Review and remove unnecessary plugins/themes that could provide a POP chain for exploitation.

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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 Coupon X plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'coupon-x' or similar, or query the wp_options table for the active_plugins option to see if Coupon X is among installed plugins
    Affected if The Coupon X plugin folder exists in wp-content/plugins/ and the plugin is active
  2. Determine the installed version of Coupon X
    Open the main plugin PHP file (usually coupon-x.php or similar in the plugin folder) and read the Version header from the plugin comment block, or query the wp_options table for the option_name containing 'coupon_x_version'
    Affected if The version number is 1.3.5 or lower (or no version is displayed, indicating an unpatched version)
  3. Verify the capture_email AJAX action exists in the plugin
    Search the plugin PHP files for 'capture_email' or 'wp_ajax_capture_email' or 'wp_ajax_nopriv_capture_email' to confirm the vulnerable AJAX handler is registered
    Affected if The capture_email AJAX action is found in the plugin code, meaning the vulnerable endpoint is exposed
  4. Confirm authenticated users can access the vulnerable action
    Check the plugin code to see if the AJAX action is registered with wp_ajax_ (requiring auth) and verify the capability check (if any) allows Contributor-level users, or test accessing the action with a Contributor-role account
    Affected if The AJAX handler does not properly validate user capabilities or allows Contributor-level access (users with Contributor role or higher)
  5. Check for potential POP chain sources on the site
    Review all installed plugins and themes for known PHP Object Injection vulnerabilities or deserialization sinks that could form a POP chain when combined with Coupon X
    Affected if Other plugins or themes on the site contain deserialization mechanisms (like unserialize() on user-controlled data) that could be chained with CVE-2024-12627

You are affected if Coupon X plugin version 1.3.5 or lower is installed and active, the capture_email AJAX action is present and accessible to Contributor-level users, and any other plugin/theme on the site provides a POP chain for exploitation.

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 Coupon X plugin to version 1.3.6 or later to patch the deserialization vulnerability. Review and remove unnecessary plugins/themes that could provide a POP chain for exploitation.

Recommended fix Moderate confidence

Update to the latest version of the Coupon X plugin (version higher than 1.3.5)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate 'Coupon X: Discount Pop Up, Promo Code Pop Ups, Announcement Pop Up, WooCommerce Popups'
  4. Click 'Update now' if an update is available, or manually download the latest version from the WordPress plugin repository
  5. Verify the update installs a version higher than 1.3.5

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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