Yith Woocommerce Product Add OnsWordPress extension · Yithemes

CVE-2024-35680

MEDIUM · 5.3 CVSS v3.1 Published 2024-06-10

Fix available

A fix is available. Upgrade to 4.9.3 or later.

See remediation →

62/100

Remediation priority · Elevated

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS) vulnerability in YITHEMES YITH WooCommerce Product Add-Ons yith-woocommerce-product-add-ons.This issue affects YITH WooCommerce Product Add-Ons: from n/a through <= 4.9.2.

Technical summary

dbcve analysis · moderate confidence

A Basic (stored) Cross-Site Scripting (XSS) vulnerability exists in the YITH WooCommerce Product Add-Ons plugin (versions up to and including 4.9.2) where script-related HTML tags are not properly neutralized, allowing attackers to inject malicious scripts into product addon fields.

MitigationUpdate the YITH WooCommerce Product Add-Ons plugin to the latest version beyond 4.9.2. If immediate patching is not possible, implement output encoding and input validation on all product addon fields as a compensating control.

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

Affected products & versions

NVD · CPE data

Yith Woocommerce Product Add OnsWordPress extension

Affected:< 4.9.3

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: None
User interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Verify YITH WooCommerce Product Add-Ons plugin is installed

Navigate to WordPress admin > Plugins or check wp-content/plugins for 'yith-woocommerce-product-add-ons' directory

Affected if Plugin is present in the WordPress installation
Check installed plugin version

Go to WordPress admin > Plugins > YITH WooCommerce Product Add-Ons and view the version number, or read the main plugin file header

Affected if Version is 4.9.2 or lower (less than 4.9.3)
Identify if product addon fields are configured

Navigate to YITH > Product Add-Ons in WordPress admin and review the addon fields list for any products

Affected if One or more product addon fields exist in the system
Inspect addon field configurations for stored XSS payloads

Check the addon field labels and options directly in the database table wp_posts (post_type = yith_wapo_set) or export addon configurations and review for suspicious HTML/script tags

Affected if Any addon field contains unsanitized HTML script tags or event handlers like onload, onerror, onclick

You are affected if the YITH WooCommerce Product Add-Ons plugin version is below 4.9.3 AND product addon fields are configured, particularly if those fields accept free-text input that could contain malicious scripts.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Upgrade available Upgrade to 4.9.3 or later

Fixed in 4.9.3

Interim mitigation

Update the YITH WooCommerce Product Add-Ons plugin to the latest version beyond 4.9.2. If immediate patching is not possible, implement output encoding and input validation on all product addon fields as a compensating control.

Recommended fix High confidence

4.9.3

Backup your WordPress site and database before proceeding with any updates
Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
Find 'YITH WooCommerce Product Add-Ons' in the plugin list
Click 'Update Now' if an update is available, or manually upload version 4.9.3 or later of the plugin
After updating, verify the plugin version is 4.9.3 or higher in the plugins list
Test that product add-ons function correctly on your WooCommerce product pages

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

Consultation2.0 h
Implementation2.0 h
Testing2.0 h
Review / QA1.0 h

7.0 hours of engineering $1,240

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,984.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

patchstack.comThird Party Advisory
patchstack.com
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-35680 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2024-35680?

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.

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

At a glance

A fix existsUpgrade to 4.9.3 or later

Severity 5.3 Medium

Exploit likelihood EPSS, next 30 days 0.3%

Affects: Yith Woocommerce Product Add Ons

Remediation

Need this fixed?

Fix this in Yith Woocommerce Product Add Ons 7 hrs · Moderate

Typical engagement from $1,240

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2024-35680 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References