dbcve.org
Tabs For WoocommerceWordPress extension · Wpbranch

CVE-2024-13831

HIGH · 7.2 CVSS v3.1 Published 2025-02-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 Tabs for WooCommerce plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 1.0.0 via deserialization of untrusted input in the 'product_has_custom_tabs' function. 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, which means this vulnerability has no impact unless another plugin or theme containing a POP chain is installed on the site. If a POP chain is present via an additional plugin or theme installed on the target system, it may allow the attacker to perform actions like delete arbitrary files, retrieve sensitive data, or execute code depending on the POP chain present.

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 Tabs for WooCommerce plugin for WordPress is vulnerable to PHP Object Injection via unsafe deserialization of untrusted input in the 'product_has_custom_tabs' function. Authenticated attackers with Shop Manager-level access can inject arbitrary PHP objects. Exploitation requires a POP chain to be present in another installed plugin or theme.

MitigationUpdate the plugin to a patched version when available. Until then, restrict Shop Manager access to trusted users only and audit installed plugins/themes for known 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
Tabs For WoocommerceWordPress extension
Affected:= 1.0.0

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 the Tabs for WooCommerce plugin is installed
    Check your WordPress plugins directory or WordPress admin under Plugins > Installed Plugins for 'Tabs for WooCommerce' or 'Wpbranch Tabs For Woocommerce'
    Affected if The plugin is present and active in the WordPress installation
  2. Confirm the exact plugin version
    In WordPress admin, go to Plugins > Installed Plugins and find the version number listed for 'Tabs for WooCommerce'
    Affected if Version is 1.0.0 (the only affected version)
  3. Locate the vulnerable function in plugin code
    Check the plugin files for the 'product_has_custom_tabs' function - typically in the main plugin file or includes folder
    Affected if The function exists and contains an unserialize() call on user-supplied data
  4. Identify users with Shop Manager role
    In WordPress admin, go to Users and filter or check for users assigned the Shop Manager role
    Affected if Any untrusted user has Shop Manager-level access to the WordPress admin
  5. Audit for POP chain candidates
    Review all other active plugins and the active theme for known PHP Object Injection POP chains - check for __wakeup, __destruct, or __toString magic methods that could be chained
    Affected if Any installed plugin or theme contains a gadget chain that could be combined with this unserialize vulnerability

You are affected if the plugin version is exactly 1.0.0, the vulnerable function contains unsafe deserialization, and an attacker with Shop Manager access could leverage a POP chain from another plugin or theme.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to a patched version when available. Until then, restrict Shop Manager access to trusted users only and audit installed plugins/themes for known POP chains that could be chained with this vulnerability.

Fix this in Tabs For Woocommerce Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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