dbcve.org
Variation SwatchesWordPress extension · Themehunk

CVE-2023-28688

MEDIUM · 5.4 CVSS v3.1 Published 2024-12-09
Fix available
A fix is available. Upgrade to 1.2.8 or later.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in ThemeHunk TH Variation Swatches allows Cross Site Request Forgery.This issue affects TH Variation Swatches: from n/a through 1.2.7.

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

Cross-Site Request Forgery (CSRF) vulnerability in ThemeHunk TH Variation Swatches plugin allows attackers to trick authenticated administrators into performing unintended configuration changes. The plugin lacks proper nonce validation on state-changing operations, enabling malicious requests to be forged via social engineering or malicious links.

MitigationUpdate to the latest version of TH Variation Swatches when available. In the interim, enforce admin session validity timeouts and educate administrators about avoiding clicking untrusted links while logged in.

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 SwatchesWordPress extension
Affected:< 1.2.8

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

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

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. Identify if Themehunk Variation Swatches plugin is installed
    Navigate to WordPress admin plugins page and locate 'Themehunk Variation Swatches' or 'TH Variation Swatches' in the installed plugins list
    Affected if Plugin is present in the plugins directory regardless of activation status
  2. Determine installed plugin version
    Check the plugin header in the main plugin file (typically in wp-content/plugins/th-variation-swatches/ or similar path) for the 'Version' field, or view the plugin details in WordPress admin plugins page
    Affected if Version number is lower than 1.2.8 (e.g., 1.2.7, 1.2.6, 1.0.0, etc.)
  3. Verify plugin is active
    Confirm the plugin status shows as 'Active' on the WordPress plugins admin page
    Affected if Plugin is currently activated on the WordPress site
  4. Confirm admin user sessions exist
    Check if any administrator-level user accounts exist on the WordPress site (via Users > All Users page)
    Affected if At least one administrator user account is present on the site

The environment is affected if Themehunk Variation Swatches plugin is installed with a version lower than 1.2.8 and the plugin is active with administrator accounts present, as the CSRF vulnerability can be exploited through social engineering targeting logged-in administrators.

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 1.2.8 or later
Fixed in 1.2.8
Interim mitigation

Update to the latest version of TH Variation Swatches when available. In the interim, enforce admin session validity timeouts and educate administrators about avoiding clicking untrusted links while logged in.

Recommended fix High confidence

1.2.8 or later

  1. Backup your WordPress site and database before updating
  2. Navigate to WordPress Admin > Plugins > Installed Plugins
  3. Find 'TH Variation Swatches' (or Variation Swatches by ThemeHunk)
  4. Click 'Update now' to update to the latest version, or manually upload version 1.2.8 or later if auto-update is not available
  5. Verify the plugin version shows 1.2.8 or higher after updating
  6. Test the variation swatches functionality on your product pages to ensure the update did not break existing functionality

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

Fix this in Variation Swatches 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 the upgrade done

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-2023-28688 — 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-28688 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