CVE-2026-2916: Jeg Kit for Elementor (WordPress plugin) · Information Exposure
Affects Jeg Kit for Elementor (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 4.3 Medium.
Data as of 30 Oct 2026, 20:25 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 1 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| jegthemeJeg Kit for Elementor – Powerful Addons for Elementor, Widgets & Templates for WordPress | Affected
| Fixed in– |
AI-suggested
Until a fix is available, restrict Contributor-level access carefully and monitor for updates from the vendor. Avoid granting Contributor or higher privileges to untrusted users.
Description
The Jeg Kit for Elementor plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 3.1.1 via the `enqueue_scripts()` method in `class/dashboard/class-dashboard.php`. The plugin injects a `JkitDashboardOption` JavaScript object containing full plugin inventory (names, versions, paths, active status), system environment details (WordPress version, PHP version, site URLs, server capabilities), and potentially third-party API credentials (Mailchimp API key via `jkit_user_data`) as an inline script on the `post.php` admin page. Because this data is output without any capability check beyond post editing access, any authenticated user with Contributor-level access or above can view this sensitive configuration data by inspecting the page source. This makes it possible for authenticated attackers, with Contributor-level access and above, to extract sensitive site configuration data, installed plugin details, and potentially third-party API keys.
References
- wordfence.com/threat-intel/vulnerabilities/id/a420a8b5-e43e-4c0d-86f3-b35f11efdf46?source=cve (opens in a new tab)
- plugins.trac.wordpress.org/browser/jeg-elementor-kit/tags/3.0.3/class/dashboard/class-dashboard.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/jeg-elementor-kit/tags/3.0.3/class/dashboard/class-dashboard.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/jeg-elementor-kit/tags/3.0.3/class/dashboard/class-dashboard.php (opens in a new tab)
- plugins.trac.wordpress.org/changeset?old_path=%2Fjeg-elementor-kit/tags/3.1.1&new_path=%2Fjeg-elementor-kit/tags/3.1.2 (opens in a new tab)