CVE-2024-12600
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 · uneditedThe Custom Product Tabs Lite for WooCommerce plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 1.9.0 via deserialization of untrusted input from the 'frs_woo_product_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 · moderate confidenceThe Custom Product Tabs Lite for WooCommerce plugin for WordPress is vulnerable to PHP Object Injection in all versions up to 1.9.0 via unsafe deserialization of the 'frs_woo_product_tabs' parameter. Authenticated attackers with Shop Manager-level access or higher can inject PHP objects. While no POP chain exists in the plugin itself, a POP chain from another plugin or theme could enable remote code execution.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm plugin is installedNavigate to WordPress Admin > Plugins or inspect the wp-content/plugins directory for 'yith-woocommerce-product-tabs-lite' or 'custom-product-tabs-lite' folderAffected if The plugin folder exists in the WordPress installation
-
Identify installed versionIn WP Admin > Plugins, locate the Custom Product Tabs Lite plugin and read the version number from the plugin details; alternatively, open the main plugin PHP file and check the 'Version' header in the plugin comment blockAffected if Version is 1.9.0 or lower
-
Verify authenticated access existsCheck WordPress user roles at Users > All Users and confirm whether any accounts have Shop Manager, Administrator, or higher-level roles assignedAffected if At least one user with Shop Manager privileges or above exists on the site
-
Check for vulnerable parameter exposureReview plugin settings or intercept HTTP requests to identify if the 'frs_woo_product_tabs' parameter is being processed; this may be visible in POST requests when saving product tab configurations in the WooCommerce product editorAffected if The plugin processes the frs_woo_product_tabs parameter without sanitization (this is the deserialization entry point)
If the plugin is installed with version 1.9.0 or lower AND a user with Shop Manager-level access exists AND the frs_woo_product_tabs parameter is in use, the environment is vulnerable to PHP Object Injection.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpdate the plugin to the latest version beyond 1.9.0 once available, or remove the plugin if no patch is released. If updates are not possible immediately, restrict Shop Manager-level access until the patch is applied.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2024-12600 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-12600 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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