Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-13141: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in devitemsllc HT Mega – Absolute Addons For Elementor

0
Medium
VulnerabilityCVE-2025-13141cvecve-2025-13141cwe-79
Published: Fri Nov 21 2025 (11/21/2025, 08:28:13 UTC)
Source: CVE Database V5
Vendor/Project: devitemsllc
Product: HT Mega – Absolute Addons For Elementor

Description

The HT Mega – Absolute Addons For Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's Gutenberg blocks in all versions up to, and including, 3.0.0 due to insufficient input validation on user-supplied HTML tag names. This is due to the lack of a tag name whitelist allowing dangerous tags like 'script', 'iframe', and 'object' to be injected even though tag_escape() is used for sanitization. While some blocks use esc_html() for content, this can be bypassed using JavaScript encoding techniques (unquoted strings, backticks, String.fromCharCode()). 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.

AI-Powered Analysis

AILast updated: 11/28/2025, 09:43:41 UTC

Technical Analysis

The HT Mega – Absolute Addons For Elementor plugin for WordPress suffers from a stored cross-site scripting (XSS) vulnerability identified as CVE-2025-13141. This vulnerability is due to improper neutralization of input during web page generation (CWE-79). Specifically, the plugin fails to properly validate and sanitize user-supplied HTML tag names in its Gutenberg blocks, allowing dangerous tags such as <script>, <iframe>, and <object> to be injected. Although the plugin uses tag_escape() for sanitization, it lacks a whitelist of allowed tags, enabling attackers to bypass this protection. Some blocks use esc_html() for content sanitization, but this can be circumvented using JavaScript encoding techniques like unquoted strings, backticks, and String.fromCharCode(). Exploitation requires authenticated access at contributor level or higher, enabling an attacker to inject arbitrary JavaScript that executes whenever a user accesses the infected page. This can lead to session hijacking, privilege escalation, or data exfiltration. The vulnerability affects all versions up to and including 3.0.0, with no patches currently available. The CVSS v3.1 score is 6.4, reflecting network attack vector, low attack complexity, privileges required, no user interaction, and impacts on confidentiality and integrity with no availability impact. No known exploits have been reported in the wild as of the publication date.

Potential Impact

For European organizations, this vulnerability can lead to significant security risks if exploited. Since the attack requires contributor-level access, insider threats or compromised accounts can be leveraged to inject malicious scripts. The injected scripts can steal session cookies, perform actions on behalf of users, or redirect users to malicious sites, compromising user data confidentiality and integrity. Organizations relying on WordPress sites with this plugin, especially those with multiple contributors or less stringent access controls, face increased risk of website defacement, data leakage, or further exploitation through chained attacks. The lack of availability impact means service disruption is unlikely, but the reputational damage and potential regulatory consequences under GDPR for data breaches could be severe. Additionally, the widespread use of WordPress in Europe, including government, education, and commercial sectors, amplifies the potential impact.

Mitigation Recommendations

Immediate mitigation steps include restricting contributor-level access to trusted users only and auditing existing user permissions to minimize risk. Organizations should monitor their WordPress sites for unusual content changes or injected scripts within pages using the HT Mega plugin. Employing a Web Application Firewall (WAF) with rules to detect and block XSS payloads targeting this plugin can reduce exploitation risk. Until an official patch is released, disabling or removing the HT Mega – Absolute Addons For Elementor plugin is advisable if feasible. Developers and site administrators should implement strict input validation and sanitization, including whitelisting allowed HTML tags and attributes. Regularly updating WordPress core and plugins, and applying security best practices such as Content Security Policy (CSP) headers, can further mitigate impact. Finally, educating contributors about the risks of injecting untrusted HTML content can reduce accidental exploitation.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-11-13T18:55:09.559Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69202539cf2d47c3899a7b24

Added to database: 11/21/2025, 8:39:21 AM

Last enriched: 11/28/2025, 9:43:41 AM

Last updated: 1/7/2026, 8:56:07 AM

Views: 67

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats