Ht MegaWordPress extension · Hasthemes

CVE-2024-2084

MEDIUM · 5.4 CVSS v3.1 Published 2024-05-02
Fix available
A fix is available. Upgrade to 2.4.7 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
The HT Mega – Absolute Addons For Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's lightbox widget in all versions up to, and including, 2.4.6 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers with contributor-level and above permissions 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 confidence

The HT Mega – Absolute Addons For Elementor WordPress plugin versions up to 2.4.6 contains a stored XSS vulnerability in its lightbox widget. Authenticated attackers with contributor-level or higher permissions can inject malicious JavaScript through unsanitized user-supplied attributes, which executes when other users access the compromised pages.

MitigationUpdate the HT Mega – Absolute Addons For Elementor plugin to version 2.4.7 or later, which contains the fix for this vulnerability. Alternatively, remove the plugin if not needed or restrict contributor-level user permissions until the update can be applied.

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
Affected:< 2.4.7

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 HT Mega plugin version
    Navigate to WordPress dashboard > Plugins and locate HT Mega - Absolute Addons For Elementor. Note the installed version number and compare it to the affected range (versions prior to 2.4.7).
    Affected if The installed version is earlier than 2.4.7
  2. Verify lightbox widget is in use
    Review pages, posts, or Elementor layouts where the HT Mega lightbox widget has been added. Check if the widget is actively published on the site.
    Affected if The lightbox widget is present and enabled on any public-facing page
  3. Inspect lightbox widget configuration for malicious scripts
    Edit pages containing the lightbox widget and examine the widget settings for any unexpected or encoded JavaScript in attribute fields such as link URLs, text, or media sources.
    Affected if Unexpected script tags or javascript: URLs are found in the lightbox widget attributes

The environment is affected if HT Mega plugin version is below 2.4.7 and the lightbox widget is actively used 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 2.4.7 or later
Fixed in 2.4.7
Interim mitigation

Update the HT Mega – Absolute Addons For Elementor plugin to version 2.4.7 or later, which contains the fix for this vulnerability. Alternatively, remove the plugin if not needed or restrict contributor-level user permissions until the update can be applied.

Recommended fix High confidence

HT Mega – Absolute Addons For Elementor version 2.4.7

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'HT Mega – Absolute Addons For Elementor' in the plugin list
  4. If an update is available, click 'Update Now' to update to version 2.4.7
  5. Alternatively, navigate to Dashboard > Updates and select the plugin to update
  6. After updating, verify the current version is 2.4.7 or later

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

Fix this in Ht Mega Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-2084 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