CVE-2026-2600
Stored XSS in ElementsKit Elementor Simple Tab Widget
Publication date: 2026-04-04
Last updated on: 2026-04-04
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wpmet | elementskit | to 3.7.9 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The ElementsKit Elementor Addons and Templates plugin for WordPress has a Stored Cross-Site Scripting (XSS) vulnerability in the Simple Tab widget. This vulnerability exists in the 'ekit_tab_title' parameter due to insufficient input sanitization and output escaping of user-supplied attributes.
Authenticated attackers with contributor-level access or higher can inject arbitrary web scripts into pages. These scripts execute whenever any user accesses the injected page, potentially compromising user security.
How can this vulnerability impact me? :
This vulnerability allows attackers with contributor-level access to inject malicious scripts into web pages. When other users visit these pages, the malicious scripts execute in their browsers.
The impact includes potential theft of user data, session hijacking, defacement of the website, or other malicious actions performed by the injected scripts.
The CVSS score of 6.4 indicates a medium severity, with low attack complexity but requiring some privileges (contributor-level access).
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability involves stored cross-site scripting via the 'ekit_tab_title' parameter in the Simple Tab widget of the ElementsKit Elementor Addons and Templates plugin for WordPress. Detection involves identifying pages or posts where the 'ekit_tab_title' parameter might contain malicious scripts injected by authenticated users with contributor-level access or higher.
Since the vulnerability is related to stored XSS in WordPress plugin data, detection can be performed by searching the database or exported content for suspicious script tags or JavaScript event handlers within the 'ekit_tab_title' fields.
- Use SQL queries on the WordPress database to search for script tags in the relevant plugin data, for example: SELECT * FROM wp_postmeta WHERE meta_key LIKE '%ekit_tab_title%' AND meta_value LIKE '%<script>%';
- Use command-line tools like grep to scan exported WordPress content or backups for suspicious script tags in 'ekit_tab_title' fields.
- Monitor HTTP traffic for suspicious payloads or unusual POST requests to pages that allow editing of the Simple Tab widget content.
What immediate steps should I take to mitigate this vulnerability?
The primary mitigation step is to update the ElementsKit Elementor Addons and Templates plugin to a version later than 3.7.9 where the vulnerability is fixed.
The fix involves sanitizing and escaping the 'ekit_tab_title' parameter output using the kses function to allow only permitted HTML tags and attributes, preventing malicious script injection.
- Update the plugin to the latest version where the patch is applied (post version 3.7.9).
- Restrict contributor-level and higher user permissions to trusted users only, minimizing the risk of malicious script injection.
- Review and clean existing content for injected scripts in the 'ekit_tab_title' fields.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows authenticated attackers with contributor-level access to inject arbitrary web scripts via stored cross-site scripting (XSS). This can lead to unauthorized access to user data or session hijacking when users access the injected pages.
Such unauthorized access or data exposure could potentially violate data protection regulations like GDPR or HIPAA, which require safeguarding personal and sensitive information against unauthorized access or disclosure.
However, the provided information does not explicitly state the direct impact on compliance with these standards.