dbcve.org
Jetwidgets For ElementorWordPress extension · Crocoblock

CVE-2024-2507

MEDIUM · 5.4 CVSS v3.1 Published 2024-04-09
Fix available
A fix is available. Upgrade to 1.0.17 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 widget button URL in all versions up to, and including, 1.0.16 due to insufficient input sanitization and output escaping on user supplied attributes. 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 plugin for WordPress is vulnerable to Stored Cross-Site Scripting (XSS) via the widget button URL parameter. The vulnerability exists in all versions up to and including 1.0.16 due to insufficient input sanitization and output escaping on user-supplied attributes, allowing authenticated attackers with contributor-level access to inject arbitrary JavaScript that executes when users access affected pages.

MitigationUpdate the JetWidgets For Elementor plugin to version 1.0.17 or later to obtain the patched version with proper input sanitization and output escaping. Audit existing content for any injected malicious scripts.

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

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 JetWidgets For Elementor plugin is installed
    Log into WordPress admin, navigate to Plugins > Installed Plugins, and look for 'JetWidgets For Elementor' or 'Crocoblock Jetwidgets For Elementor' in the list
    Affected if The plugin is present in the WordPress installation
  2. Check the installed plugin version
    In the plugins list, locate the version number displayed beneath the JetWidgets For Elementor plugin name
    Affected if The version number is below 1.0.17 (for example, 1.0.16, 1.0.15, etc.)
  3. Identify JetWidgets button widgets in use
    Edit pages or posts using the Elementor editor, or search the database for post content containing 'jet-button' or jetwidgets-related shortcodes/elements that include URL fields
    Affected if Any JetWidgets button widgets with a URL parameter configured are present in published content
  4. Inspect button widget URL parameters for unsanitized input
    Edit each JetWidgets button widget, examine the URL field in the widget settings, and check if the value contains unescaped HTML or script tags
    Affected if The URL field accepts and stores raw input without sanitization or if saved content shows unescaped characters in the URL attribute

A user is affected if the JetWidgets For Elementor plugin version is below 1.0.17 AND any JetWidgets button widgets with URL parameters exist in their content.

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.17 or later
Fixed in 1.0.17
Interim mitigation

Update the JetWidgets For Elementor plugin to version 1.0.17 or later to obtain the patched version with proper input sanitization and output escaping. Audit existing content for any injected malicious scripts.

Recommended fix High confidence

1.0.17

  1. 1. Back up your WordPress site and database before making any changes.
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard.
  3. 3. Locate the Jetwidgets For Elementor plugin in the list.
  4. 4. If an update is available, click 'Update Now' to update to the latest version.
  5. 5. Alternatively, download version 1.0.17 from the WordPress plugin repository and upload it manually via Plugins > Add New > Upload Plugin.
  6. 6. After updating, verify the plugin version shows 1.0.17 or higher.
  7. 7. Test the affected widget functionality to ensure the update does not break existing content.

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
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
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,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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