dbcve.org
Wc BuilderWordPress extension · Hasthemes

CVE-2025-68533

MEDIUM · 6.5 CVSS v3.1 Published 2025-12-24
Fix available
A fix is available. Upgrade to 1.2.1 or later.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable

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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in HasThemes WC Builder wc-builder allows Stored XSS.This issue affects WC Builder: from n/a through <= 1.2.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

Stored Cross-site Scripting (XSS) vulnerability in HasThemes WC Builder plugin allows attackers to inject malicious JavaScript through unsanitized user input. The payload is persistently stored on the server and executes in the browsers of users who view the affected content, potentially leading to session hijacking or credential theft.

MitigationUpdate WC Builder to the latest patched version. Until then, implement output encoding/sanitization on all user inputs and consider disabling the plugin if update is unavailable.

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
Wc BuilderWordPress 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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/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. Locate WC Builder plugin installation
    Check your WordPress plugins directory or WordPress admin panel under Plugins > Installed Plugins. Look for 'HasThemes WC Builder' or 'WC Builder' plugin. Note the installed version number displayed there.
    Affected if Plugin is installed and version is below 1.2.1
  2. Verify plugin version
    In WordPress admin, go to Plugins > Installed Plugins. Find WC Builder and compare the displayed version number to 1.2.1. If it shows 1.2.0 or lower, the version is vulnerable.
    Affected if Installed version is less than 1.2.1
  3. Identify active product/customization templates
    Check if WC Builder templates are actively used on the site. Go to WC Builder settings or templates section in WordPress admin. Look for any created product layouts, archive layouts, or custom designs.
    Affected if WC Builder templates are actively configured or in use on the site
  4. Inspect stored content in database
    Query your WordPress database for recent entries in posts, postmeta, or any WC Builder-related tables that contain unsanitized HTML/script tags in user-editable fields such as product titles, short descriptions, or custom content blocks.
    Affected if Database contains entries with raw script tags or javascript: URIs in fields that accept user input
  5. Check browser console for XSS errors
    Navigate to pages using WC Builder templates (product pages, shop pages) and open browser developer console. Look for any script execution errors or warnings related to injected content.
    Affected if Console shows unexpected script errors or executed code from user-supplied input fields

You are affected if HasThemes WC Builder plugin is installed with a version below 1.2.1 and the plugin's customizable content fields are being used to display user-editable text on the site.

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 WC Builder to the latest patched version. Until then, implement output encoding/sanitization on all user inputs and consider disabling the plugin if update is unavailable.

Recommended fix High confidence

WC Builder version 1.2.1

  1. Create a complete backup of your WordPress site and database before making any changes
  2. Update WC Builder plugin to version 1.2.1 or later through the WordPress admin dashboard (Plugins > Add New > Upload or WordPress repository if available)
  3. Alternatively, update via FTP by uploading the new version files to wp-content/plugins/wc-builder/
  4. Clear any server-side and CDN caches after updating
  5. Verify the update was successful by checking the plugin version in Plugins > Installed Plugins
  6. Test that the XSS vulnerability is no longer exploitable by reviewing any user input fields in the WC Builder functionality

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

Fix this in Wc Builder 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-2025-68533 — 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-2025-68533 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