dbcve.org
Jetwidgets For ElementorWordPress extension · Crocoblock

CVE-2024-4626

MEDIUM · 5.4 CVSS v3.1 Published 2024-06-20
Fix available
A fix is available. Upgrade to 1.0.18 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 JetWidgets For Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘layout_type’ and 'id' parameters in all versions up to, and including, 1.0.17 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, 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 JetWidgets For Elementor WordPress plugin fails to properly sanitize the 'layout_type' and 'id' parameters before storing them and rendering them in output, allowing authenticated contributors+ to inject malicious JavaScript that persists in the database and executes when other users view affected pages.

MitigationUpdate to version 1.0.18 or later which includes proper input sanitization for the affected parameters; alternatively, implement output escaping where the layout_type and id values are rendered.

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
Jetwidgets For ElementorWordPress extension
Affected:< 1.0.18

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. Confirm JetWidgets For Elementor is installed
    Access WordPress admin dashboard, go to Plugins > Installed Plugins, and look for 'JetWidgets For Elementor' or 'Crocoblock Jetwidgets For Elementor' in the list. Alternatively, check the plugin directory wp-content/plugins/ for a folder named jetwidgets-for-elementor or similar.
    Affected if The plugin is installed and active
  2. Check the installed plugin version
    In the WordPress Plugins admin page, locate JetWidgets For Elementor and view the version number displayed beneath the plugin name. Compare this version against the affected range of versions prior to 1.0.18.
    Affected if The installed version is lower than 1.0.18 (for example, 1.0.17, 1.0.16, etc.)
  3. Identify pages using JetWidgets with layout settings
    Query the WordPress database wp_postmeta table for meta keys related to jetwidgets layout settings. Look for meta entries containing '_elementor_data' or similar meta_keys that may contain serialized data with 'layout_type' or 'id' parameters used by the plugin widgets.
    Affected if Posts or pages contain Elementor data with JetWidgets widget settings that include 'layout_type' or 'id' parameters
  4. Inspect stored parameter values for malicious content
    Examine the values in wp_postmeta where jetwidgets-related meta_keys are present. Check if the stored values for 'layout_type' or 'id' contain unexpected HTML script tags, javascript: URIs, or event handler attributes like onload, onerror, or onmouseover.
    Affected if The stored values contain unescaped HTML script tags or JavaScript event handlers indicating exploitation

You are affected if the JetWidgets For Elementor plugin is installed with a version lower than 1.0.18 and any pages using the plugin contain persisted malicious script content in layout_type or id parameter values.

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 1.0.18 or later
Fixed in 1.0.18
Interim mitigation

Update to version 1.0.18 or later which includes proper input sanitization for the affected parameters; alternatively, implement output escaping where the layout_type and id values are rendered.

Recommended fix High confidence

1.0.18

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'JetWidgets For Elementor' in the plugin list
  4. Check if the current version is below 1.0.18
  5. If vulnerable, click 'Update Now' to update the plugin to the latest version
  6. Alternatively, navigate to Dashboard > Updates and update the plugin from there
  7. After updating, verify the plugin version shows 1.0.18 or higher

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

Fix this in Jetwidgets For Elementor Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
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,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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