Ht MegaWordPress extension · Hasthemes
CVE-2024-1421
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 · uneditedThe HT Mega – Absolute Addons For Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘border_type’ attribute of the Post Carousel widget in all versions up to, and including, 2.4.4 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
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 · high confidenceThe HT Mega plugin's Post Carousel widget fails to properly sanitize and escape the 'border_type' attribute, allowing authenticated users with contributor-level access to inject malicious JavaScript via stored XSS. This script executes whenever other users access affected pages.
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 MegaWordPress extension
<= 2.4.4CVSS 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.
-
Check installed HT Mega versionNavigate to Plugins > Installed Plugins in WordPress admin, locate 'HT Mega - Absolute Addons For Elementor', and note the version number displayed.Affected if Version is 2.4.4 or lower
-
Identify Post Carousel widget usageReview pages, posts, or Elementor templates that use the HT Mega Post Carousel widget. Check Elementor editor or page content for the 'Post Carousel' widget from HT Mega.Affected if Post Carousel widget is present on any published page
-
Audit contributor-level user accountsGo to Users > All Users in WordPress admin and identify any accounts with the 'Contributor' role.Affected if At least one contributor-level user account exists in the system
Environment is affected if HT Mega version is 2.4.4 or lower, the Post Carousel widget is in use on a live page, and contributor-level users have editing access to that widget.
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 · scopedUpdate HT Mega – Absolute Addons For Elementor to version 2.4.5 or later. If immediate update is not possible, restrict contributor-level user permissions or disable the Post Carousel widget until the patch can be applied.
Update to the latest available version of HT Mega plugin (version higher than 2.4.4)
- Log in to WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate 'HT Mega – Absolute Addons For Elementor' in the plugin list
- Check if an update is available for the plugin
- If update is available, click 'Update Now' to install the latest version
- Alternatively, navigate to Dashboard > Updates and select the plugin to update
- After updating, verify the new version number reflects a version higher than 2.4.4
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Ht Mega
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2024-1421 — 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-1421 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