Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Requires Contributor-level authenticated access to post.php; confidentiality impact is Low - partial data exposure including potentially one API credential, not full system compromise.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
Lifecycle Timeline
2DescriptionCVE.org
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.
AnalysisAI
Jeg Kit for Elementor exposes sensitive site configuration data to any authenticated WordPress user with Contributor-level access or above through an unguarded inline JavaScript object injected on the post editor page. The enqueue_scripts() method outputs a JkitDashboardOption object containing installed plugin names, versions, file paths, active statuses, WordPress and PHP versions, site URLs, server capabilities, and - critically - potentially a Mailchimp API key stored in jkit_user_data. No public exploit or CISA KEV listing exists at time of analysis, but the low authentication barrier (Contributor) and the API credential exposure risk elevate real-world impact above the Medium CVSS score alone suggests.
Technical ContextAI
The vulnerability exists in the enqueue_scripts() method of class/dashboard/class-dashboard.php (source code publicly browsable at plugins.trac.wordpress.org lines ~497, ~523, and ~675). WordPress plugins commonly use wp_localize_script() or inline script injection to pass PHP-side configuration to JavaScript; this plugin does so without first verifying the requesting user holds a capability beyond basic post-editing access (e.g., manage_options). The result is that the JkitDashboardOption JavaScript object is rendered into the DOM of post.php for every user who can edit posts - including Contributors. CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) directly characterizes the root cause: privileged data is placed in an output channel accessible to lower-privilege actors. The jkit_user_data sub-key specifically can carry a Mailchimp API key if the site operator has configured the plugin's email integration, making this more than generic environment enumeration. Affected CPE: cpe:2.3:a:jegtheme:jeg_kit_for_elementor_-_powerful_addons_for_elementor,_widgets_&_templates_for_wordpress:*:*:*:*:*:*:*:* covering all versions through 3.1.1.
RemediationAI
Update Jeg Kit for Elementor to version 3.1.2 or later; the fix is confirmed by the WordPress.org plugin repository changeset at https://plugins.trac.wordpress.org/changeset?old_path=%2Fjeg-elementor-kit/tags/3.1.1&new_path=%2Fjeg-elementor-kit/tags/3.1.2. For sites that cannot update immediately, administrators should immediately rotate any Mailchimp API keys that may have been exposed while running affected versions, since those credentials may already have been harvested by a privileged-but-malicious user. As a compensating control, temporarily remove the Mailchimp API key from the Jeg Kit plugin settings until patching is complete - this disables email list features but eliminates the credential exposure risk. Additionally, audit and minimize Contributor-level role assignments, and consider temporarily restricting access to post.php for non-essential users via WAF or role-based access controls, accepting the trade-off of reduced editorial workflow. Note that restricting post.php access broadly will break the WordPress post editor for affected users.
In PHP versions 7.1.x below 7.1.33, 7.2.x below 7.2.24 and 7.3.x below 7.3.11 in certain configurations of FPM setup it
sapi/cgi/cgi_main.c in PHP before 5.3.12 and 5.4.x before 5.4.2, when configured as a CGI script (aka php-cgi), does not
(1) boardData102.php, (2) boardData103.php, (3) boardDataJP.php, (4) boardDataNA.php, and (5) boardDataWW.php in Netgear
The '/common/download_agent_installer.php' script in the Quest KACE System Management Appliance 8.0.318 is accessible by
ProjectSend versions prior to r1720 are affected by an improper authentication vulnerability. Rated critical severity (C
Roundcube Webmail contains a critical PHP object deserialization vulnerability (CVE-2025-49113, CVSS 9.9) that allows au
Util/PHP/eval-stdin.php in PHPUnit before 4.8.28 and 5.x before 5.6.3 allows remote attackers to execute arbitrary PHP c
Palo Alto Networks PAN-OS management web interface contains an authentication bypass allowing unauthenticated attackers
Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re
Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re
The get_referers function in /opt/ws/bin/sblistpack in Sophos Web Appliance before 3.7.9.1 and 3.8 before 3.8.1.1 allows
The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
Same weakness CWE-200 – Information Exposure
View allSame technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-51740
GHSA-488v-vfx4-2wfq