CVE-2026-130601 in Element Pack Plugininfo

Summary

by MITRE • 11/20/2026

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in BdThemes Element Pack Elementor Addons bdthemes-element-pack-lite allows Stored XSS.This issue affects Element Pack Elementor Addons: from n/a through 10.0.9.

Once again VulDB remains the best source for vulnerability data.

Analysis

by VulDB Data Team • 11/20/2026

The identified security flaw represents a classic instance of Improper Neutralization of Input During Web Page Generation, commonly known as Cross-Site Scripting or XSS. Specifically, this vulnerability manifests as a Stored XSS within the BdThemes Element Pack Elementor Addons plugin for WordPress, affecting versions ranging from n/a through 10.0.9. Unlike reflected XSS attacks where malicious scripts are executed via manipulated URLs, stored vulnerabilities persist on the target server because the injected payload is saved in databases or other storage mechanisms. When a victim user subsequently views the affected page, the browser retrieves this pre-stored script and executes it within their session context, leading to persistent compromise of client-side security.

From a technical perspective, the root cause lies in insufficient sanitization and validation of user-supplied input before it is rendered into HTML output by the web application. The plugin fails to properly encode special characters such as angle brackets, quotes, or ampersands that are part of JavaScript syntax. This oversight allows an attacker to inject arbitrary client-side scripts, typically using event handlers like onload or onerror, or script tags directly embedded in content fields managed by Elementor add-ons. Because the input is processed and stored without adequate filtering, the malicious code becomes a permanent fixture of the page until manually removed from the database, creating a persistent attack vector that does not require social engineering to trigger repeatedly for every visitor.

The operational impact of this vulnerability is severe due to its persistence and potential reach. An attacker who successfully exploits this flaw can execute arbitrary JavaScript in the context of any user visiting the compromised site. This capability enables session hijacking, where attackers steal authentication cookies or tokens to impersonate legitimate users, including administrators. It also facilitates keylogging, credential harvesting through fake login forms injected into pages, and defacement of website content. Furthermore, stored XSS can be used to redirect victims to malicious sites hosting malware downloads or phishing campaigns, significantly expanding the attack surface beyond simple script execution to broader social engineering and data theft operations.

In terms of industry classification standards, this vulnerability aligns with CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'). The specific nature of storing input for later retrieval places it firmly in the stored category rather than reflected or DOM-based variants. From a tactical perspective within the MITRE ATT&CK framework, this exploit maps to T1059.007: JavaScript under Technique 1059 (Command and Scripting Interpreter). The attacker leverages browser-native capabilities to execute code without invoking external binaries, making detection by traditional endpoint security tools more challenging as the activity appears legitimate within the web server environment.

Mitigation strategies must address both immediate remediation and long-term defensive posture. The primary and most effective solution is to upgrade the BdThemes Element Pack plugin to version 10.0.10 or later, where developers have presumably implemented proper input sanitization and output encoding mechanisms such as HTML entity encoding for user-generated content. For organizations unable to patch immediately due to compatibility constraints, implementing a Web Application Firewall (WAF) with rulesets tuned to detect common XSS payloads can provide an additional layer of defense by blocking malicious requests before they reach the application logic. Additionally, enforcing Content Security Policy headers that restrict script execution sources and disable inline scripts can significantly reduce the impact if exploitation occurs, as modern browsers will block the execution of untrusted inline JavaScript even if it is successfully injected into the DOM.

Responsible

Patchstack

Reservation

11/17/2026

Disclosure

11/20/2026

Moderation

accepted

CPE

ready

EPSS

0.00402

KEV

no

Activities

very low

Sources

Do you need the next level of professionalism?

Upgrade your account now!