dbcve.org
Path TraversalWeakness · CWE-22

CVE-2024-38772

MEDIUM · 6.5 CVSS v3.1 Published 2024-08-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Crocoblock JetWidgets for Elementor and WooCommerce allows PHP Local File Inclusion.This issue affects JetWidgets for Elementor and WooCommerce: from n/a through 1.1.7.

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

Path traversal vulnerability in Crocoblock JetWidgets for Elementor and WooCommerce (versions up to 1.1.7) allows attackers to read arbitrary files on the server through improper path validation, enabling PHP local file inclusion via manipulated directory traversal sequences.

MitigationUpdate JetWidgets to the latest version once available, or disable the plugin until a security patch is released. Restrict file system permissions as a defense-in-depth measure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 plugin installation
    In WordPress admin, navigate to Plugins > Installed Plugins and look for 'JetWidgets' or check the wp-content/plugins directory for the jetwidgets folder
    Affected if The plugin is installed and present in the WordPress environment
  2. Check installed JetWidgets version
    In WordPress admin, go to Plugins > Installed Plugins, find JetWidgets, and note the version number displayed; alternatively, check the main plugin file header in wp-content/plugins/jetwidgets/jetwidgets.php for the 'Version' tag
    Affected if The installed version is 1.1.7 or any version lower than 1.1.7
  3. Confirm plugin is active
    In WordPress admin > Plugins > Installed Plugins, verify that JetWidgets shows as 'Active' under the plugin status
    Affected if The plugin is active and therefore exposed to the vulnerability
  4. Identify accessible file-inclusion widgets
    Review available JetWidgets elements in the Elementor page builder editor; look for any widgets that handle file display, content import, or template inclusion that accept file paths as parameters
    Affected if Any JetWidgets widget that accepts file path parameters is accessible and potentially exploitable

A user is affected if JetWidgets for Elementor/WooCommerce is installed, active, and running version 1.1.7 or below, with file-handling widgets accessible on the 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update JetWidgets to the latest version once available, or disable the plugin until a security patch is released. Restrict file system permissions as a defense-in-depth measure.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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