dbcve.org
Custom Product Tabs For WoocommerceWordPress extension · Yikesinc

CVE-2024-11465

HIGH · 7.2 CVSS v3.1 Published 2025-01-07
Fix available
A fix is available. Upgrade to after 1.8.5 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.8.5 via deserialization of untrusted input in the 'yikes_woo_products_tabs' post meta 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 is vulnerable to PHP Object Injection in all versions up to 1.8.5. The vulnerability stems from deserialization of untrusted input via the 'yikes_woo_products_tabs' post meta parameter, allowing authenticated attackers with Shop Manager-level access to inject arbitrary PHP objects.

MitigationUpdate to a patched version of the plugin when available. Until then, disable the plugin or restrict administrative access to prevent exploitation.

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.8.5

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. Confirm the plugin is installed
    Navigate to WordPress admin > Plugins and look for 'Yikesinc Custom Product Tabs For Woocommerce' or check the plugin files in wp-content/plugins/ for a folder containing 'custom-product-tabs' or 'yikes-woo'
    Affected if The plugin is present on the site
  2. Check the installed plugin version
    In WordPress admin > Plugins, click on the plugin to view details, or open the main plugin PHP file and look for the 'Version' header in the plugin comment block
    Affected if The version is 1.8.5 or lower
  3. Verify WooCommerce is active
    In WordPress admin > Plugins, confirm WooCommerce is installed and activated. This plugin requires WooCommerce to function
    Affected if WooCommerce is active and the vulnerable plugin is installed
  4. Check for Shop Manager users
    Go to WordPress admin > Users and review user roles. Shop Manager is a WooCommerce-specific role. Check if any users have Shop Manager role
    Affected if There are users with Shop Manager role or higher admin access, and the vulnerable plugin is installed
  5. Inspect the vulnerable post meta
    Query the WordPress database for post meta with meta_key 'yikes_woo_products_tabs': SELECT * FROM wp_postmeta WHERE meta_key = 'yikes_woo_products_tabs' LIMIT 10; (adjust wp_ prefix if different)
    Affected if Records exist with this meta key, indicating the plugin's vulnerable feature is in use

A site is affected if the Yikesinc Custom Product Tabs For Woocommerce plugin version 1.8.5 or lower is installed, WooCommerce is active, and users with Shop Manager or higher privileges exist.

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.8.5
Interim mitigation

Update to a patched version of the plugin when available. Until then, disable the plugin or restrict administrative access to prevent exploitation.

Recommended fix High confidence

Custom Product Tabs For WooCommerce version 1.8.6 or later

  1. Log in to the WordPress admin dashboard with Shop Manager-level or Administrator privileges
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Custom Product Tabs For WooCommerce' in the plugin list
  4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. Alternatively, download the latest version from the WordPress Plugin Repository and upload it via Plugins > Add New > Upload Plugin
  6. After updating, verify the plugin is running version 1.8.6 or higher
  7. If no update is available in the WordPress admin, manually download version 1.8.6 or later from the WordPress Plugin Repository and reinstall
Caveat Minimal risk - patch update unlikely to introduce breaking changes; always backup before updating

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
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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