dbcve.org
Information ExposureWeakness · CWE-200

CVE-2026-4106

MEDIUM · 5.3 CVSS v3.1 Published 2026-04-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 Addons for Elementor WordPress plugin before 3.0.7 contains an unauthenticated AJAX action returning some PII (such as full name, city, state and country) of customers who placed orders in the last 7 days

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

The HT Mega Addons for Elementor plugin before version 3.0.7 has an unauthenticated AJAX action that exposes sensitive customer PII including full name, city, state, and country for orders placed in the last 7 days. This allows any anonymous user to access this data without authentication, representing a privacy violation and potential compliance concern.

MitigationUpgrade to HT Mega Addons for Elementor version 3.0.7 or later to patch the vulnerable AJAX endpoint. If immediate upgrading is not feasible, consider restricting access to the affected AJAX action via server-side configuration or temporarily disabling the plugin.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 Addons for Elementor is installed
    Check your WordPress plugins directory (wp-content/plugins/htmega-addons-for-elementor) or view the installed plugins list in wp-admin > Plugins
    Affected if The plugin folder 'htmega-addons-for-elementor' exists in your plugins directory or appears in WordPress admin plugins list
  2. Check the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins > HT Mega Addons for Elementor and note the version number displayed, or inspect the main plugin file header in htmega-addons-for-elementor/htmega-addons-for-elementor.php
    Affected if The displayed version is lower than 3.0.7 (for example: 3.0.6, 3.0.5, etc.)
  3. Identify the vulnerable AJAX endpoint
    Review the plugin PHP files for AJAX actions that handle order data. Look for wp_ajax_nopriv_ hooks or wp_ajax_ hooks that process order-related queries without capability checks. Common paths: includes/ajax-handler.php or similar ajax directories within the plugin
    Affected if You find an AJAX action registered with 'nopriv' (unauthenticated access) that retrieves order customer data including name, city, state, or country fields
  4. Test unauthenticated AJAX access to order data
    If you can safely do so in a non-production environment, send a request to your site's wp-admin/admin-ajax.php?action=the_plugin_ajax_action (the specific action name from step 3) without providing any authentication cookies or credentials
    Affected if The response returns customer PII (full names, addresses, order details) without requiring login credentials
  5. Confirm order data timeframe matches vulnerability scope
    Examine the AJAX response data or the underlying PHP code to determine if the query filters to orders from the last 7 days
    Affected if The exposed data includes recent orders (within the last 7 days) containing customer full name, city, state, and country

You are affected if HT Mega Addons for Elementor is installed with a version lower than 3.0.7 and an unauthenticated AJAX endpoint exposing customer order PII is accessible on your 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to HT Mega Addons for Elementor version 3.0.7 or later to patch the vulnerable AJAX endpoint. If immediate upgrading is not feasible, consider restricting access to the affected AJAX action via server-side configuration or temporarily disabling the plugin.

Recommended fix High confidence

HT Mega Addons for Elementor version 3.0.7

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate HT Mega Addons for Elementor in the plugin list
  4. Check if the current version is below 3.0.7
  5. If vulnerable, click 'Update now' if an update is available, or manually download version 3.0.7 from the WordPress plugin repository and reinstall
  6. After updating, verify the plugin version shows 3.0.7 or higher
  7. Test that the website frontend and Elementor functionality still work correctly

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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 locally
dbcve dependency scanner

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