dbcve.org
Custom Product Tabs For WoocommerceWordPress extension · Webbuilder143

CVE-2024-12721

HIGH · 7.2 CVSS v3.1 Published 2024-12-21
Fix available
A fix is available. Upgrade to after 1.2.4 or later.
See remediation →
78/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 Custom Product Tabs For WooCommerce plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 1.2.4 via deserialization of untrusted input from the 'wb_custom_tabs' parameter. This makes it possible for authenticated attackers, with Shop Manager-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 Custom Product Tabs For WooCommerce plugin for WordPress versions up to 1.2.4 is vulnerable to PHP Object Injection via deserialization of untrusted input in the 'wb_custom_tabs' parameter. Authenticated attackers with Shop Manager-level access can inject PHP objects. While no POP chain exists in the plugin itself, additional plugins or themes on the target system could provide one, enabling arbitrary file deletion, data retrieval, or code execution.

MitigationUpdate the Custom Product Tabs For WooCommerce plugin to the latest version. If no patched version is available, restrict Shop Manager role permissions or disable the plugin until a fix is released. Review installed plugins and themes for potential POP chains that could be chained with this vulnerability.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Custom Product Tabs For WoocommerceWordPress extension
Affected:<= 1.2.4

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

CVSS:3.1/AV:N/AC:L/PR:H/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 plugin is installed
    Check if the Custom Product Tabs For WooCommerce plugin directory exists in wp-content/plugins/ (commonly named something like custom-product-tabs-for-woocommerce or similar)
    Affected if The plugin directory is present on the system
  2. Check installed version
    Open the main plugin PHP file or readme.txt in the plugin directory and locate the Version header. Compare it to the affected range: <= 1.2.4
    Affected if The version number found is 1.2.4 or lower
  3. Confirm WooCommerce is active
    Check if WooCommerce plugin is installed and active in WordPress (wp-content/plugins/woocommerce/)
    Affected if WooCommerce is active, as this plugin is a WooCommerce extension
  4. Verify Shop Manager role exists
    In WordPress admin, go to Users > Users and check for users with Shop Manager role, or query the wp_roles option in the database for the shop_manager role
    Affected if The Shop Manager role is defined and any user has that role assigned
  5. Test vulnerable parameter exposure
    Review the plugin code for handling of the 'wb_custom_tabs' parameter - typically found in form submissions or AJAX handlers that call unserialize() on this input
    Affected if The plugin code contains an unserialize() call on the 'wb_custom_tabs' parameter without prior sanitization

You are affected if the plugin is installed with version 1.2.4 or lower, WooCommerce is active, and the vulnerable unserialize() call on the wb_custom_tabs parameter exists in the codebase.

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
Upgrade available Upgrade to a release after 1.2.4
Interim mitigation

Update the Custom Product Tabs For WooCommerce plugin to the latest version. If no patched version is available, restrict Shop Manager role permissions or disable the plugin until a fix is released. Review installed plugins and themes for potential POP chains that could be chained with this vulnerability.

Recommended fix Moderate confidence

1.2.5 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Custom Product Tabs For WooCommerce' in the plugin list
  4. Check the current version number to confirm it is 1.2.4 or below
  5. If an update is available, click 'Update Now' to upgrade to the latest version
  6. Alternatively, navigate to Dashboard > Updates to update all plugins
  7. After updating, verify the plugin version is 1.2.5 or higher in Plugins > Installed Plugins

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

Fix this in Custom Product Tabs For Woocommerce Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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