dbcve.org
Jeg Elementor KitWordPress extension · Jegtheme

CVE-2024-47390

MEDIUM · 5.4 CVSS v3.1 Published 2024-10-05
Fix available
A fix is available. Upgrade to 2.6.9 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in jegtheme Jeg Elementor Kit jeg-elementor-kit allows Stored XSS.This issue affects Jeg Elementor Kit: from n/a through <= 2.6.8.

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

This is a Stored Cross-Site Scripting (XSS) vulnerability in the Jeg Elementor Kit WordPress plugin. The vulnerability allows an attacker with low privileges (likely contributor or author role) to inject malicious JavaScript code into plugin settings or content areas. This payload is then stored on the server and executed in the browsers of other users who view the affected pages, potentially leading to session hijacking, credential theft, or defacement.

MitigationUpdate Jeg Elementor Kit to the latest version (2.6.9 or higher) which contains the patched fix for this XSS vulnerability. Before updating in production, test the update on a staging environment to ensure compatibility with the site's theme and other plugins.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Jeg Elementor KitWordPress extension
Affected:< 2.6.9

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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 Jeg Elementor Kit plugin is installed
    Check the WordPress plugins directory for the jeg-elementor-kit folder, or log into WordPress admin and navigate to Plugins > Installed Plugins to confirm Jeg Elementor Kit appears in the list.
    Affected if The plugin is present in the WordPress installation
  2. Identify the installed version number
    In WordPress admin, go to Plugins > Installed Plugins and locate Jeg Elementor Kit; the version number is displayed below the plugin name. Alternatively, check the main plugin file header in wp-content/plugins/jeg-elementor-kit/ for the 'Version' comment.
    Affected if Unable to determine version or version is unknown
  3. Compare version against affected range
    Compare the installed version to the affected range: any version below 2.6.9 (such as 2.6.8, 2.6.7, 2.6.0, 1.x.x, etc.) is vulnerable.
    Affected if Installed version is less than 2.6.9
  4. Confirm plugin is active
    In WordPress admin > Plugins > Installed Plugins, verify that Jeg Elementor Kit shows as 'Active' rather than 'Inactive' or 'Must-Use'.
    Affected if Plugin is active on the site

If Jeg Elementor Kit is installed, active, and the version is below 2.6.9, the environment is affected by this Stored XSS vulnerability.

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
Upgrade available Upgrade to 2.6.9 or later
Fixed in 2.6.9
Interim mitigation

Update Jeg Elementor Kit to the latest version (2.6.9 or higher) which contains the patched fix for this XSS vulnerability. Before updating in production, test the update on a staging environment to ensure compatibility with the site's theme and other plugins.

Recommended fix High confidence

Jeg Elementor Kit 2.6.9

  1. Backup your WordPress site database and files before performing any updates
  2. Navigate to your WordPress admin dashboard > Plugins
  3. Locate Jeg Elementor Kit in the installed plugins list
  4. If an update is available, click 'Update Now' to update to the latest version
  5. Alternatively, you can update via WordPress > Dashboard > Updates or upload the plugin manually via FTP
  6. After updating, verify the plugin version shows 2.6.9 or later in the plugins list
  7. Clear any caching layers (site cache, CDN cache) after the update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Jeg Elementor Kit 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 the upgrade done

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-2024-47390 — 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-2024-47390 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