dbcve.org
Ht MegaWordPress extension · Hasthemes

CVE-2024-3989

MEDIUM · 5.4 CVSS v3.1 Published 2024-05-14
Fix available
A fix is available. Upgrade to 2.5.1 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 Gallery Justify Widget in all versions up to, and including, 2.5.0 due to insufficient input sanitization and output escaping on user supplied attributes. 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 confidence

The HT Mega – Absolute Addons For Elementor WordPress plugin versions up to 2.5.0 contains a stored XSS vulnerability in the Gallery Justify Widget. Authenticated attackers with contributor-level permissions can inject arbitrary JavaScript through unsanitized widget attributes. The malicious payload persists in the database and executes whenever users access the affected pages.

MitigationUpdate HT Mega – Absolute Addons For Elementor to version 2.5.1 or later, which implements proper input sanitization and output escaping. If immediate update is not possible, consider disabling the Gallery Justify Widget until the patch 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.5.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
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. Verify HT Mega plugin is installed
    Navigate to WordPress Admin > Plugins and locate 'HT Mega - Absolute Addons For Elementor', or check the installed_plugins option in wp_options table, or inspect /wp-content/plugins/ht-mega-for-elementor/ directory
    Affected if Plugin is present in the WordPress installation
  2. Check the installed plugin version
    In WordPress Admin > Plugins, click on the plugin to view version details, or read the 'Version' header from /wp-content/plugins/ht-mega-for-elementor/ht-mega.php file, or run: wp plugin list --name='ht-mega-for-elementor'
    Affected if Version is 2.5.0 or lower (any version < 2.5.1)
  3. Identify pages using the Gallery Justify Widget
    Search WordPress database in wp_postmeta for meta_key '_elementor_data' containing 'ht-gallery-justify' or similar widget identifiers, or use Elementor editor to check pages for this specific widget
    Affected if The Gallery Justify Widget from HT Mega is present on any published page or post
  4. Inspect widget settings for malicious scripts
    Examine the stored _elementor_data in wp_postmeta for the affected pages; decode the JSON and look for suspicious JavaScript in attributes like 'gallery_images', 'link', or custom HTML fields within the Gallery Justify widget configuration
    Affected if Unsanitized user input containing <script> tags, javascript:, or event handlers (onclick, onerror, etc.) is found in widget attributes

User is affected if HT Mega plugin version is below 2.5.1 AND the Gallery Justify Widget is in use on any published content with unsanitized script payloads in its settings.

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.5.1 or later
Fixed in 2.5.1
Interim mitigation

Update HT Mega – Absolute Addons For Elementor to version 2.5.1 or later, which implements proper input sanitization and output escaping. If immediate update is not possible, consider disabling the Gallery Justify Widget until the patch can be applied.

Recommended fix High confidence

HT Mega – Absolute Addons For Elementor version 2.5.1

  1. 1. Log in to the WordPress admin dashboard with administrator privileges
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'HT Mega – Absolute Addons For Elementor' in the plugin list
  4. 4. Check if the current version is below 2.5.1
  5. 5. If an update is available, click 'Update Now' to upgrade to version 2.5.1
  6. 6. Verify the update completed successfully and the plugin shows version 2.5.1
  7. 7. Test the Gallery Justify Widget functionality to ensure it still works correctly after the update

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
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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