CVE-2026-116594: Jeg Kit for Elementor <= 3.3.0 - Authenticated (Subscriber+) Stored Cross-Site Scripting via 'Biographical Info' Field

Published Nov 18, 2026
·
Updated

The Jeg Kit for Elementor – Powerful Addons for Elementor, Widgets & Templates for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'description' parameter in all versions up to, and including, 3.3.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Successful execution requires a published page containing both a Post Author widget in userbio mode (rendering the attacker's biography) and any legitimate jkitclientlogo widget, so that client-logo.js is enqueued and the loadCarousel handler fires against the forged widget markup from the bio field.

Affected Software

1 affected component
Jegstudio Jeg Kit for Elementor<=3.3.0

Event History

Nov 18, 2026
CVE Published
via MITRE·01:32 PM
Data Sourced
via MITRE·01:32 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·02:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who can exploit this issue?

An attacker needs an authenticated WordPress account with at least Subscriber-level access. No user interaction is required from the attacker after they inject the payload, but a user must later visit an affected published page for the script to execute.

2

Are all sites using the affected plugin configuration vulnerable in practice?

No. Exploitation requires a published page that uses a Post Author widget in user_bio mode and renders the attacker's biography, plus a legitimate jkit_client_logo widget anywhere needed to enqueue client-logo.js. Without those conditions, the described execution path is not available.

3

What versions are affected?

Jeg Kit for Elementor versions through 3.3.0, including 3.3.0, are affected. The provided information does not identify a fixed version.

4

What can be done if an update is not immediately available?

Restrict or remove Subscriber-and-higher accounts that are not trusted to edit their biographical information. Also avoid publishing pages that combine a Post Author widget in user_bio mode with a jkit_client_logo widget until remediation is available.

5

How can administrators look for exploitation attempts?

Review biography or description content for untrusted HTML or script-like widget markup, particularly for accounts with Subscriber-level access. Prioritize review where those biographies are displayed on published pages using Post Author in user_bio mode alongside a jkit_client_logo widget.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203