dbcve.org
Ht MegaWordPress extension · Hasthemes

CVE-2023-50901

MEDIUM · 6.1 CVSS v3.1 Published 2023-12-29
Fix available
A fix is available. Upgrade to after 2.3.8 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 HasThemes HT Mega – Absolute Addons For Elementor allows Reflected XSS.This issue affects HT Mega – Absolute Addons For Elementor: from n/a through 2.3.8.

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

A reflected Cross-site Scripting (XSS) vulnerability exists in the HT Mega – Absolute Addons For Elementor WordPress plugin. The vulnerability allows attackers to inject malicious JavaScript code through unsanitized user input that gets reflected in the web page without proper output encoding.

MitigationUpdate HT Mega – Absolute Addons for Elementor to the latest version to receive the vendor patch that properly sanitizes and encodes user input before reflecting it in web 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
Affected:<= 2.3.8

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 installed plugin version
    Navigate to WordPress admin > Plugins > Installed Plugins, look for 'HT Mega - Absolute Addons For Elementor' and note the version number displayed
    Affected if The displayed version is 2.3.8 or lower
  2. Verify plugin files exist
    Check the wp-content/plugins/ht-mega-for-elementor directory exists and contains the main plugin file
    Affected if The plugin directory and files are present on the server
  3. Confirm Elementor is active
    In WordPress admin > Plugins, verify that Elementor Website Builder is installed and activated
    Affected if Elementor is active, as this plugin extends Elementor functionality
  4. Identify reflected parameter usage
    Review website access logs for GET/POST requests to pages using HT Mega addons, looking for unsanitized parameters that might reflect in output (common XSS vectors include search, id, or addon-specific parameters)
    Affected if Requests contain user-supplied input that gets reflected in page output without encoding
  5. Check for XSS indicators in logs
    Search web server access and error logs for patterns like <script, javascript:, onerror=, onload= targeting URLs containing 'ht-mega' or elementor addon paths
    Affected if Suspicious XSS payload patterns appear in logs associated with HT Mega endpoints

Your environment is affected if HT Mega - Absolute Addons For Elementor version 2.3.8 or lower is installed and active, and user input can be reflected in output without sanitization.

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 a release after 2.3.8
Interim mitigation

Update HT Mega – Absolute Addons for Elementor to the latest version to receive the vendor patch that properly sanitizes and encodes user input before reflecting it in web pages.

Recommended fix Moderate confidence

Latest version of HT Mega – Absolute Addons For Elementor (version 2.3.9 or later)

  1. Log in to your WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'HT Mega – Absolute Addons For Elementor' in the plugin list
  4. Check if an update is available and update to the latest version
  5. Alternatively, download the latest version from WordPress.org and upload via Plugins > Add New > Upload Plugin
  6. After updating, verify the plugin version is above 2.3.8

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
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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