dbcve.org
Jeg Elementor KitWordPress extension · Jegtheme

CVE-2024-29101

MEDIUM · 5.4 CVSS v3.1 Published 2024-03-19
Fix available
A fix is available. Upgrade to 2.6.3 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 allows Stored XSS.This issue affects Jeg Elementor Kit: from n/a through 2.6.2.

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 · moderate confidence

A stored XSS vulnerability in Jeg Elementor Kit allows attackers to inject malicious JavaScript code through unsanitized user input, which is then executed when other users view the affected content in the web page.

MitigationUpdate to the latest version of Jeg Elementor Kit if a security patch is available; otherwise, implement proper input validation and output encoding on all user-supplied data fields in the affected plugin components.

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.3

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 is installed
    Check your WordPress plugins directory or WordPress admin under Plugins > Installed Plugins for 'Jeg Elementor Kit' or 'Jegtheme Jeg Elementor Kit'
    Affected if The plugin is not listed or not found in the system
  2. Determine installed version
    In WordPress admin, go to Plugins > Installed Plugins and look for the version number listed under Jeg Elementor Kit, or check the plugin header in the main plugin file (typically /wp-content/plugins/jeg-elementor-kit/jeg-elementor-kit.php)
    Affected if The version number is lower than 2.6.3 (e.g., 2.6.2, 2.6.1, 2.5.0, etc.)
  3. Confirm plugin is active
    In WordPress admin under Plugins > Installed Plugins, verify that Jeg Elementor Kit shows as 'Active'
    Affected if The plugin is active and the version is below 2.6.3
  4. Identify user input forms
    Review pages using Jeg Elementor Kit widgets that accept user input (such as forms, comment sections, login/registration widgets, or any widget that stores and displays user-submitted content)
    Affected if The plugin contains any frontend-facing forms or user input widgets and the version is below 2.6.3

You are affected if Jeg Elementor Kit is installed, active, and running a version lower than 2.6.3, with any user input functionality exposed on your site.

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.3 or later
Fixed in 2.6.3
Interim mitigation

Update to the latest version of Jeg Elementor Kit if a security patch is available; otherwise, implement proper input validation and output encoding on all user-supplied data fields in the affected plugin components.

Recommended fix Moderate confidence

Jeg Elementor Kit 2.6.3

  1. Log in to your WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find Jeg Elementor Kit in the plugin list
  4. Check if an update is available (version should show below 2.6.3)
  5. Click 'Update Now' to update to version 2.6.3
  6. Alternatively, download version 2.6.3 from the WordPress plugin repository or your account at jegtheme.com
  7. Deactivate and delete the current plugin version, then upload and install version 2.6.3
  8. After update, clear any caching plugins and test the site frontend to ensure the plugin functions correctly

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

Fix this in Jeg Elementor Kit Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,330
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,728.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-29101 — 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-29101 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