dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-2600

MEDIUM · 6.4 CVSS v3.1 Published 2026-04-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable 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 ElementsKit Elementor Addons and Templates plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'ekit_tab_title' parameter in the Simple Tab widget in all versions up to, and including, 3.7.9 due to insufficient input sanitization and output escaping on user supplied attributes. 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.

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 · high confidence

The ElementsKit plugin for WordPress contains a stored XSS vulnerability in the Simple Tab widget's 'ekit_tab_title' parameter. Insufficient input sanitization and lack of output escaping on user-supplied attributes allows authenticated contributors or higher to inject malicious JavaScript that executes when other users access affected pages.

MitigationUpdate ElementsKit to version 3.8.0 or later which implements proper input sanitization and output escaping. Audit existing content for injected scripts.

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
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/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 ElementsKit plugin is installed
    Navigate to WordPress admin dashboard > Plugins and confirm ElementsKit Elementor Addons appears in the installed plugins list
    Affected if ElementsKit plugin is present on the WordPress site
  2. Identify installed ElementsKit version
    In Plugins list, look for the version number under the ElementsKit plugin entry, or check the plugin header file via file system at wp-content/plugins/elements-kit-lite/elements-kit-lite.php
    Affected if Version is below 3.8.0 (the fixed version)
  3. Confirm Simple Tab widget is in use
    Review pages/posts created with Elementor editor and check if the Simple Tab widget from ElementsKit has been added to any content
    Affected if Simple Tab widget is actively used on any published page or post
  4. Inspect stored ekit_tab_title values in database
    Query the WordPress postmeta table for meta_key containing 'ekit_tab' or 'pro_ekit_tab', or use a database tool to search post_content for 'elements-kit' and 'tab' shortcode or widget configurations
    Affected if Tab titles contain unsanitized script tags, event handlers, or suspicious JavaScript patterns
  5. Review recent contributor-level user activity
    Check WordPress user roles and audit logs for any contributor accounts, then review content they created or modified for unusual tab widget configurations
    Affected if Contributor-level user has created or modified Simple Tab widget content with injected attributes

The site is affected if ElementsKit plugin version is below 3.8.0 AND the Simple Tab widget is in use, creating potential for stored XSS execution.

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

Update ElementsKit to version 3.8.0 or later which implements proper input sanitization and output escaping. Audit existing content for injected scripts.

Recommended fix Moderate confidence

ElementsKit Elementor Addons and Templates plugin version higher than 3.7.9 (check WordPress plugin repository for latest stable release)

  1. 1. Update the ElementsKit Elementor Addons and Templates plugin to the latest available version from the WordPress plugin repository.
  2. 2. After updating, verify the Simple Tab widget settings to ensure no malicious 'ekit_tab_title' values were previously injected.
  3. 3. If malicious content was found, remove the injected scripts and resave the affected pages.

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-2600 — 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-2600 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