dbcve.org
SwatchlyWordPress extension · Hasthemes

CVE-2023-23792

HIGH · 8.8 CVSS v3.1 Published 2023-07-11
Fix available
A fix is available. Upgrade to 1.2.1 or later.
See remediation →
95/100
Remediation priority · Urgent
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 HasThemes Swatchly plugin <= 1.2.0 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 confidence

Cross-Site Request Forgery (CSRF) vulnerability in HasThemes Swatchly plugin versions 1.2.0 and below allows attackers to trick authenticated users into performing unintended actions by sending malicious requests. The CVSS 8.8 score indicates the vulnerability can lead to significant impact if successfully exploited.

MitigationUpdate the Swatchly plugin to the latest version immediately. If no patched version is available, disable the plugin until a fix is released, or implement anti-CSRF tokens 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 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
SwatchlyWordPress extension
Affected:< 1.2.1

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 Swatchly plugin installation
    Check your WordPress plugins directory (wp-content/plugins/) for a folder named 'swatchly', or access the Plugins page in WordPress admin and look for 'HasThemes Swatchly' in the installed plugins list
    Affected if The Swatchly plugin folder exists in the plugins directory or appears in the WordPress admin plugins list
  2. Determine the installed version
    Open the main plugin file (usually swatchly.php) in the swatchly folder and locate the version defined in the plugin header (often via 'Version:' comment) or check the WordPress admin Plugins page where version numbers are displayed
    Affected if The version displayed is 1.2.0 or below, or the version cannot be determined (meaning it predates proper version tracking)
  3. Verify the plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and confirm the Swatchly plugin shows as 'Active'
    Affected if The plugin is activated - CSRF attacks require an authenticated session, which only occurs when the plugin is active
  4. Confirm lack of CSRF protection exists
    Inspect the plugin's admin PHP files (particularly form handlers and action processors in the swatchly folder) for presence of nonce verification or CSRF tokens - look for wp_verify_nonce, check_admin_referer, or similar security token functions
    Affected if Form submissions and admin actions in the plugin lack nonce verification (no wp_verify_nonce or check_admin_referer calls found in form processing code)

You are affected if the HasThemes Swatchly plugin is installed, active, and its version is 1.2.0 or below without evidence of CSRF token protection in the plugin code.

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.1 or later
Fixed in 1.2.1
Interim mitigation

Update the Swatchly plugin to the latest version immediately. If no patched version is available, disable the plugin until a fix is released, or implement anti-CSRF tokens as a compensating control.

Recommended fix Moderate confidence

Swatchly version 1.2.1

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the Swatchly plugin in the list
  4. Check if an update is available for Swatchly
  5. If update available, click 'Update Now' to update to version 1.2.1 or later
  6. Alternatively, navigate to Dashboard > Updates and update Swatchly from there
  7. After updating, verify the plugin version shows 1.2.1 or higher

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

Fix this in Swatchly Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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