Ht BuilderWordPress extension · Hasthemes
CVE-2024-51682
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in HasThemes HT Builder – WordPress Theme Builder for Elementor ht-builder allows Stored XSS.This issue affects HT Builder – WordPress Theme Builder for Elementor: from n/a through <= 1.3.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 confidenceStored XSS vulnerability in HT Builder WordPress plugin allows attackers to inject malicious JavaScript through unsanitized input fields. The payload is persistently stored in the database and executes when administrators or other users view the affected content in the Elementor theme builder.
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
Ht BuilderWordPress extension
< 1.3.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify HT Builder plugin is installedLog into WordPress admin dashboard, navigate to Plugins > Installed Plugins, and search for 'HT Builder' or 'Hasthemes' to confirm the plugin is present.Affected if Plugin is found in the plugins list
-
Check installed HT Builder versionIn the Plugins list, locate HT Builder and view the version number displayed beneath the plugin name. Compare this version against the affected range.Affected if Installed version is below 1.3.1
-
Confirm Elementor theme builder is activeCheck if the Elementor website builder plugin is installed and active, as the vulnerability specifically affects content viewed through Elementor's theme builder integration.Affected if Elementor is active and HT Builder templates are in use
-
Inspect stored HT Builder content for unsanitized inputAccess the WordPress database (via phpMyAdmin or command line) and query HT Builder custom post types or tables for unescaped HTML/script tags in input fields, particularly looking for <script> tags or javascript: URIs in content that should have been sanitized.Affected if Unsanitized script tags or malicious JavaScript payloads are found stored in the database
User is affected if HT Builder plugin is installed with version less than 1.3.1 and Elementor theme builder is being used with HT Builder templates containing stored malicious scripts.
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 · scoped1.3.1
Update to patched version when available; prior to patch, implement input sanitization using WordPress functions like sanitize_text_field() and output escaping with esc_html()/esc_attr() at all user input points.
1.3.1
- 1. Create a full backup of the WordPress site (database and files) before making any changes
- 2. Navigate to WordPress admin dashboard > Plugins > Installed Plugins
- 3. Find 'HT Builder – WordPress Theme Builder for Elementor' in the plugin list
- 4. Click 'Update now' if an update is available, or manually upload version 1.3.1 of the plugin
- 5. After updating, verify the plugin shows version 1.3.1 in the Plugins list
- 6. Test the affected functionality where the XSS vulnerability was reported to confirm the fix
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Ht Builder
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-51682 — 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-2024-51682 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