dbcve.org
Wc BuilderWordPress extension · Hasthemes

CVE-2024-29926

MEDIUM · 5.4 CVSS v3.1 Published 2024-03-27
Fix available
A fix is available. Upgrade to 1.0.19 or later.
See remediation →
58/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 allows Stored XSS.This issue affects WC Builder: from n/a through 1.0.18.

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

A Stored Cross-Site Scripting (XSS) vulnerability exists in HasThemes WC Builder plugin (versions up to 1.0.18). The plugin fails to properly sanitize user input during web page generation, allowing authenticated attackers to inject malicious JavaScript scripts that persist in the database and execute when other users view affected pages.

MitigationUpdate WC Builder to the latest version when available. Until then, restrict administrative access to trusted users only and implement Content Security Policy (CSP) headers to mitigate XSS execution. The fix requires implementing proper input sanitization (e.g., sanitize_text_field(), esc_html(), esc_attr()) and output encoding at all user input entry points.

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.0.19

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
None

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

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

  1. Check HasThemes WC Builder plugin version
    Navigate to WordPress admin > Plugins > Installed Plugins and locate 'HasThemes WC Builder' in the list. The version number is displayed below the plugin name.
    Affected if The displayed version is 1.0.18 or lower (versions below 1.0.19 are affected).
  2. Confirm plugin is active
    In the same Plugins list, verify that HasThemes WC Builder shows as 'Active' under the plugin status.
    Affected if The plugin is active and running a vulnerable version.
  3. Identify pages created with WC Builder
    Check your WordPress pages or WooCommerce product pages for any that were created or edited using the WC Builder functionality. Look for pages with custom WooCommerce layouts, product designs, or store customization created through this plugin.
    Affected if Any pages or products were built using the WC Builder plugin, as these are potential locations where malicious scripts could be stored.
  4. Inspect stored content for suspicious scripts
    Access your WordPress database (via phpMyAdmin or command line) and examine tables that store page/post content (typically wp_posts). Search for script tags, javascript: URIs, or on* event handlers within content fields that correspond to WC Builder pages.
    Affected if Any records in the database contain unsanitized script tags or JavaScript event handlers within content created or modified by WC Builder.

If HasThemes WC Builder version is below 1.0.19 and the plugin is active with any custom pages or products created through it, the environment is potentially affected and stored XSS payloads may exist in the database.

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.0.19 or later
Fixed in 1.0.19
Interim mitigation

Update WC Builder to the latest version when available. Until then, restrict administrative access to trusted users only and implement Content Security Policy (CSP) headers to mitigate XSS execution. The fix requires implementing proper input sanitization (e.g., sanitize_text_field(), esc_html(), esc_attr()) and output encoding at all user input entry points.

Recommended fix Moderate confidence

WC Builder version 1.0.19

  1. 1. Backup your WordPress site and database before making any changes.
  2. 2. Update WC Builder plugin to version 1.0.19 or later through the WordPress admin dashboard (Plugins > Add New > Upload or from the installed plugins list).
  3. 3. Alternatively, update via WordPress automatic updates if enabled.
  4. 4. After updating, verify the plugin version shows 1.0.19 or higher in Plugins > Installed Plugins.
  5. 5. Test the affected functionality to confirm the XSS vulnerability is remediated.

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

Fix this in Wc Builder Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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