Variation Swatches For WoocommerceWordPress extension · Variation Swatches For Woocommerce Project
CVE-2023-37975
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 · uneditedUnauth. Reflected Cross-Site Scripting (XSS) vulnerability in RadiusTheme Variation Swatches for WooCommerce plugin <= 2.3.7 versions.
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 confidenceUnauthenticated reflected Cross-Site Scripting (XSS) vulnerability in the RadiusTheme Variation Swatches for WooCommerce plugin for WordPress, affecting versions 2.3.7 and below. The vulnerability allows an attacker to inject malicious JavaScript scripts through unsanitized user input that is reflected back in the web application's response.
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
Variation Swatches For WoocommerceWordPress extension
< 2.3.8CVSS 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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.
-
Locate the plugin versionIn WordPress admin, go to Plugins > Installed Plugins, find 'Variation Swatches For WooCommerce' by RadiusTheme, and read the version number displayed below the plugin name. Alternatively, check the plugin's main PHP file header comment for the 'Version' tag.Affected if The version listed is 2.3.7 or lower, or any version below 2.3.8
-
Confirm the plugin is activeVerify that the Variation Swatches For WooCommerce plugin is currently activated in Plugins > Installed Plugins. The vulnerability requires the plugin to be active to be exploitable.Affected if The plugin shows as 'Active' under the plugin name
-
Identify the vulnerable input pointReview the site for any frontend pages that accept user input and display variation swatches (such as product pages with color/size selectors). The reflected XSS occurs when unsanitized parameters from the URL are echoed back in the page response.Affected if User-supplied parameters from the URL query string appear unmodified in the HTML source of pages using the plugin's swatch functionality
You are affected if the plugin version is below 2.3.8 and the plugin is active, with any user input from URL parameters being reflected without sanitization on product variation pages.
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.
dbcve · scoped2.3.8
Update the Variation Swatches for WooCommerce plugin to the latest patched version. If no update is available, apply input validation and output escaping to all user-controlled parameters in the affected code paths.
2.3.8
- Backup your WordPress site before making any changes
- Navigate to WordPress admin dashboard > Plugins
- Find 'Variation Swatches For WooCommerce' by RadiusTheme
- Update the plugin to version 2.3.8 or later
- Verify the update was successful by checking the installed version
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Variation Swatches For Woocommerce
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2023-37975 — 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-2023-37975 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