dbcve.org
Yith Woocommerce Product Add OnsWordPress extension · Yithemes

CVE-2023-49777

HIGH · 8.8 CVSS v3.1 Published 2023-12-31
Fix available
A fix is available. Upgrade to after 4.3.0 or later.
See remediation →
94/100
Remediation priority · Urgent
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
Deserialization of Untrusted Data vulnerability in YITH YITH WooCommerce Product Add-Ons.This issue affects YITH WooCommerce Product Add-Ons: from n/a through 4.3.0.

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 confidence

A deserialization of untrusted data vulnerability exists in the YITH WooCommerce Product Add-Ons WordPress plugin up to version 4.3.0. This type of vulnerability typically allows attackers to manipulate serialized data inputs to execute arbitrary code or perform other malicious actions.

MitigationUpdate YITH WooCommerce Product Add-Ons to the latest patched version as soon as available. If no patch exists, consider disabling the plugin until a fix is released.

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
Yith Woocommerce Product Add OnsWordPress extension
Affected:<= 4.3.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/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. Locate the YITH WooCommerce Product Add-Ons plugin
    Navigate to WordPress admin > Plugins, or inspect the wp-content/plugins directory for a folder containing 'yith-woocommerce-product-add-ons' or similar YITH add-on related files
    Affected if The plugin directory exists in the WordPress installation
  2. Determine the installed plugin version
    Check the plugin header in the main PHP file (often in the plugin root) or in readme.txt for the version number. In WordPress admin, view the plugin details under Plugins > Installed Plugins
    Affected if The version number is 4.3.0 or lower (any version up to and including 4.3.0)
  3. Confirm the plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and verify whether YITH WooCommerce Product Add-Ons shows as 'Active'
    Affected if The plugin is active and accessible to the site
  4. Check for unexpected serialized data handling
    Review server access logs and error logs for any unserialize() calls or PHP warnings related to YITH plugin files, particularly if the plugin processes external input
    Affected if The plugin processes serialized data from untrusted sources without validation

A user is affected if YITH WooCommerce Product Add-Ons version 4.3.0 or lower is installed and active in their WordPress environment.

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 4.3.0
Interim mitigation

Update YITH WooCommerce Product Add-Ons to the latest patched version as soon as available. If no patch exists, consider disabling the plugin until a fix is released.

Recommended fix Moderate confidence

YITH WooCommerce Product Add-Ons version 4.3.1 or later

  1. 1. Log in to your WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'YITH WooCommerce Product Add-Ons' in the plugin list
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. 5. Alternatively, navigate to Dashboard > Updates and apply all available updates
  6. 6. After updating, verify the plugin version is greater than 4.3.0 in Plugins > Installed Plugins

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

Fix this in Yith Woocommerce Product Add Ons Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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