dbcve.org
Ht MegaWordPress extension · Hasthemes

CVE-2024-30182

MEDIUM · 5.4 CVSS v3.1 Published 2024-03-27
Fix available
A fix is available. Upgrade to 2.4.4 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 DevItems HT Mega ht-mega-for-elementor.This issue affects HT Mega: from n/a through <= 2.4.3.

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

Cross-site scripting (XSS) vulnerability in the HT Mega for Elementor WordPress plugin (versions <= 2.4.3) allows attackers to inject malicious JavaScript code through unsanitized user input that gets rendered in web pages without proper output encoding.

MitigationUpgrade HT Mega for Elementor to version 2.4.4 or later which includes proper input sanitization and output encoding. Until patched, disable the plugin or implement WAF rules to block XSS attack patterns.

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

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
    In WordPress admin, go to Plugins > Installed Plugins and look for 'HT Mega for Elementor' in the list. Alternatively, check the file /wp-content/plugins/htmega-for-elementor/ exists.
    Affected if Plugin is installed and version is less than 2.4.4
  2. Check installed plugin version
    In WordPress admin Plugins page, click 'View Details' on HT Mega for Elementor to see the version number. Alternatively, read the main plugin file header at /wp-content/plugins/htmega-for-elementor/htmega.php and look for 'Version:' comment.
    Affected if Version displayed is 2.4.3 or lower (any version below 2.4.4)
  3. Confirm plugin is active
    In WordPress admin Plugins page, verify the plugin shows as 'Active' under the HT Mega for Elementor listing.
    Affected if Plugin is active and vulnerable version is installed
  4. Check for indicators of XSS exploitation
    Review website access logs and server logs for patterns like '<script', 'javascript:', or other XSS payloads in URLs that may target HT Mega endpoints. Also check WordPress user accounts for unauthorized creation.
    Affected if Suspicious XSS payloads found in logs targeting the plugin, or unknown admin accounts exist

User is affected if HT Mega for Elementor version 2.4.3 or lower is installed and active on their WordPress 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.4 or later
Fixed in 2.4.4
Interim mitigation

Upgrade HT Mega for Elementor to version 2.4.4 or later which includes proper input sanitization and output encoding. Until patched, disable the plugin or implement WAF rules to block XSS attack patterns.

Recommended fix High confidence

2.4.4

  1. 1. Backup your WordPress site before making any changes
  2. 2. Navigate to the WordPress admin dashboard
  3. 3. Go to Plugins > Installed Plugins
  4. 4. Find 'Ht Mega for Elementor' in the plugin list
  5. 5. If an update is available, click 'Update Now' to update to version 2.4.4 or later
  6. 6. Alternatively, download the latest version from the WordPress plugin repository and upload it manually
  7. 7. After updating, verify the plugin version shows 2.4.4 or higher
  8. 8. 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 Ht Mega Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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