dbcve.org
Jeg Elementor KitWordPress extension · Jegtheme

CVE-2024-3161

MEDIUM · 5.4 CVSS v3.1 Published 2024-05-02
Fix available
A fix is available. Upgrade to 2.6.5 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 the countdown widget's attributes in all versions up to, and including, 2.6.4 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor access or higher, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 plugin for WordPress is vulnerable to Stored Cross-Site Scripting (XSS) in the countdown widget. Authenticated attackers with contributor-level access or higher can inject malicious JavaScript through unsanitized widget attributes. The injected scripts execute whenever users access the compromised pages, allowing attackers to steal session cookies, perform actions as other users, or redirect traffic.

MitigationUpdate the Jeg Elementor Kit plugin to version 2.6.5 or later to resolve the input sanitization and output escaping issues. Review and test all countdown widgets on the site after updating.

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

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
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Jeg Elementor Kit' in the list. Note the installed version number displayed.
    Affected if The plugin is present on the site.
  2. Compare installed version against affected range
    Check if the installed version number is less than 2.6.5. If the version shows exactly 2.6.5 or higher, the version is not vulnerable.
    Affected if Installed version is less than 2.6.5.
  3. Identify countdown widgets in use
    Navigate to Pages or Posts in WordPress admin, or check Elementor layouts, for any pages using the Jeg Elementor Kit countdown widget. Use WordPress search or Elementor template search to locate pages containing the countdown element.
    Affected if The countdown widget from this plugin is present on any published page or post.
  4. Inspect countdown widget configuration for suspicious attributes
    Edit each page containing the countdown widget using Elementor editor. Review all text fields in the widget settings including labels, countdown labels, and message fields. Look for unexpected script tags, event handlers (onclick, onload, onerror), or javascript: URLs in any input field.
    Affected if The widget configuration contains unsanitized script tags, javascript: protocols, or event handlers in any text field.
  5. Check browser console for XSS errors on affected pages
    Visit pages containing the countdown widget in a browser. Open developer tools (F12) and check the Console tab for any XSS-related errors or warnings, or view the Page Source to search for unescaped HTML in the countdown widget output.
    Affected if Malicious JavaScript is executing or present in the page source.

The environment is affected if the Jeg Elementor Kit plugin is installed with version less than 2.6.5 AND the countdown widget is used on any published page, allowing stored XSS injection.

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.5 or later
Fixed in 2.6.5
Interim mitigation

Update the Jeg Elementor Kit plugin to version 2.6.5 or later to resolve the input sanitization and output escaping issues. Review and test all countdown widgets on the site after updating.

Recommended fix High confidence

2.6.5

  1. Create a complete backup of your WordPress site before making any changes
  2. Update the Jeg Elementor Kit plugin to version 2.6.5 or later through the WordPress admin dashboard (Plugins > Add New > Upload or directly from the WordPress plugin repository)
  3. Alternatively, update via WP-CLI: wp plugin update jeg-elementor-kit --version=2.6.5
  4. After updating, verify the fix by checking that the countdown widget properly sanitizes input in the plugin settings
  5. Clear any caching plugins or server-side caches to ensure the patched version is served to all users
  6. Review pages using the countdown widget to ensure no malicious scripts were previously injected

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-3161 — 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-3161 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