dbcve.org
Jeg Elementor KitWordPress extension · Jegtheme

CVE-2024-1326

MEDIUM · 5.4 CVSS v3.1 Published 2024-03-21
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
The Jeg Elementor Kit plugin for WordPress is vulnerable to Stored Cross-Site Scripting via HTML Tag attributes in all versions up to, and including, 2.6.2 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers with contributor-level and above permissions to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE-2024-29101 is likely a duplicate of this issue.

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

The Jeg Elementor Kit WordPress plugin versions up to 2.6.2 contains a stored XSS vulnerability in HTML Tag attribute handling. Attackers with contributor-level permissions can inject malicious JavaScript through unsanitized input fields, which executes when other users view the compromised pages due to insufficient output escaping.

MitigationUpdate the Jeg Elementor Kit plugin to version 2.6.3 or later which includes proper input sanitization and output escaping for HTML tag attributes. Until updated, restrict contributor-level user permissions or disable the plugin.

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 plugin installation and version
    Navigate to WordPress admin > Plugins > Installed Plugins and locate 'Jeg Elementor Kit' in the list. Note the installed version number displayed.
    Affected if The installed version is lower than 2.6.3 (for example, 2.6.2, 2.6.1, 2.6.0, etc.)
  2. Confirm contributor-level user accounts exist
    Go to WordPress admin > Users > All Users and review the role assigned to each account. Look for any users with the 'Contributor' role.
    Affected if At least one user account with Contributor role exists in the WordPress installation
  3. Inspect Elementor pages for unexpected script tags
    Using the WordPress admin, navigate to Pages > All Pages. View pages created or edited by contributors. Inspect the page source or use browser developer tools to examine HTML elements, particularly any custom HTML widgets or Elementor widgets with tag attribute settings for unexpected <script> tags or javascript: URI handlers.
    Affected if Unexpected <script> tags, event handlers (onclick, onerror, onload), or javascript: URLs are found in page content originating from contributor-edited pages

The environment is affected if Jeg Elementor Kit version is below 2.6.3 AND contributor-level users exist who could have injected malicious scripts into pages.

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 the Jeg Elementor Kit plugin to version 2.6.3 or later which includes proper input sanitization and output escaping for HTML tag attributes. Until updated, restrict contributor-level user permissions or disable the plugin.

Recommended fix High confidence

Jeg Elementor Kit 2.6.3

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Jeg Elementor Kit' in the plugin list
  4. Check if the current version is below 2.6.3
  5. If an update is available, click 'Update Now' to install version 2.6.3
  6. Alternatively, download version 2.6.3 from the WordPress plugin repository and upload manually via Plugins > Add New > Upload Plugin
  7. After updating, verify the new version number reflects 2.6.3

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
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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