CVE-2026-2916 is an authenticated information exposure vulnerability in Jeg Kit for Elementor through version 3.1.1. A Contributor or a user with higher privileges can read the JkitDashboardOption inline object on the WordPress post editor screen. The exposed data includes installed plugin details and system configuration, and can include a Mailchimp API key when the integration is configured. The issue is fixed in version 3.1.2.
| CVE | CVE-2026-2916 |
| Plugin Version | Jeg Kit for Elementor <= 3.1.1, fixed in 3.1.2 |
| All Time | 5 062 164 |
| Active installations | 300 000+ |
| Publicly Published | July 31, 2026 |
| Last Updated | August 1, 2026 |
| Researcher | Dmitrii Ignatyev |
| PoC | Yes |
| Exploit | No |
| Reference | https://www.cve.org/CVERecord?id=CVE-2026-2916 https://www.wordfence.com/threat-intel/vulnerabilities/wordpress-plugins/jeg-elementor-kit/jeg-kit-for-elementor-311-authenticated-contributor-exposure-of-sensitive-information-via-jkitdashboardoption-inline-script |
| Plugin Security Certification by CleanTalk | ![]() |
| Logo of the plugin | ![]() |
PSC by CleantalkJoin the community of developers who prioritize security. Highlight your plugin in the WordPress catalog.
Timeline
| By February 12, 2026 | Plugin testing and vulnerability detection in Jeg Kit for Elementor were completed. |
| February 12, 2026 | The vulnerability report was sent with the PoC, description, and recommendations for remediation. |
| July 31, 2026 | CVE-2026-2916 was publicly published by Wordfence. |
Discovery of the Vulnerability
The disclosure occurs when dashboard configuration is included in a post editor response. The affected enqueue_scripts() implementation in class/dashboard/class-dashboard.php prepares JkitDashboardOption from get_all_option() and adds it as inline JavaScript. The referenced source includes post.php among the screens that receive this dashboard script, extending its reach beyond the plugin settings page.
The exported object combines the plugin inventory, system information, and the contents of jkit_user_data. These values can reveal active and inactive plugins, installed versions, plugin paths, site URLs, WordPress and PHP versions, and server capabilities. When configured, the Mailchimp integration key is included under userData. Access to the post editor is sufficient to receive this data, without an administrative capability check on the export.
Understanding of Information Exposure attacks
Information exposure occurs when an application sends data to a user whose role does not authorize access to it. A WordPress Contributor can create and edit their own posts, but that access does not grant permission to inspect site-wide plugin configuration or integration credentials. Once sensitive values are written into the editor HTML, hiding the corresponding settings interface does not protect them.
The plugin inventory and environment details make it easier to identify installed components and match their versions to known vulnerabilities. Exposure of a configured Mailchimp API key can also enable actions permitted by that key. The credential impact depends on whether a key has been saved. The inventory disclosure does not depend on a Mailchimp integration being configured.
Exploiting the Information Exposure Vulnerability
The following PoC follows the reported Elementor workflow and inspects the inline object already returned to the editor. A fake Mailchimp key can be used as a marker on a disposable test installation. Preparing that marker is an administrator action and is separate from the lower privileged reproduction.
POC:
POC: Account - Contributor or higher Environment - an isolated WordPress test site with an affected Jeg Kit for Elementor release and Elementor active Optional administrator-only lab setup If no Mailchimp key is configured, use the fake marker TESTKEY-us1. Run the following query only against a disposable test database. It replaces the existing jkit_user_data option value. UPDATE wp_options SET option_value = CONCAT( 'a:1:{s:9:"mailchimp"', CHAR(59), 'a:1:{s:7:"api_key"', CHAR(59), 's:11:"TESTKEY-us1"', CHAR(59), '}}' ), autoload = 'yes' WHERE option_name = 'jkit_user_data' 1. Sign in as a Contributor or another user permitted to edit posts. 2. Go to http://127.0.0.1/wordpress/wp-admin/post-new.php. 3. Click "Edit with Elementor", then exit back to the WordPress editor. 4. Inspect the HTML source of the resulting /wp-admin/post.php page. 5. Find JkitDashboardOption in the inline script and inspect its data. 6. Confirm that plugin inventory and system details are present. If the fake key was configured, check for TESTKEY-us1 in userData.____
The database prefix may differ from wp_. CHAR(59) supplies the separators required by PHP serialization. The optional query updates an existing option and will not create a missing row. No request to Mailchimp is needed to confirm exposure of the fake marker. Inspecting the local response is enough.
Recommendations for Improved Security
Update Jeg Kit for Elementor to 3.1.2 or a newer patched release, preferably the latest supported version. If untrusted users could access the editor while a real Mailchimp key was stored, revoke and replace that key and review the integration activity. Keep post editing access limited to accounts that need it.
Developers should restrict dashboard scripts to the screens that require them and apply an appropriate current_user_can() check before returning administrative data. Build a small allowlist of editor configuration instead of exporting complete option arrays. Keep third-party credentials on the server and perform integration requests there. Test the resulting page source with Contributor and Author accounts as well as administrators.
Addressing CVE-2026-2916 keeps administrative configuration and integration credentials out of lower privileged editor responses. Plugin updates and careful control of data sent to the browser help maintain that boundary.
#WordPressSecurity #InformationExposure #MissingAuthorization #PluginSecurity #WebsiteSafety #StayProtected
Use CleanTalk solutions to improve the security of your website.

