dbcve.org
Path TraversalWeakness · CWE-22

CVE-2024-37497

HIGH · 7.7 CVSS v3.1 Published 2024-07-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
83/100
Remediation priority · High
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 JetThemeCore jet-theme-core.This issue affects JetThemeCore: from n/a through < 2.2.1.

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 JetThemeCore plugin allows attackers to access files outside the intended restricted directory through manipulation of file paths. This could enable unauthorized read access to sensitive files on the server.

MitigationUpdate JetThemeCore plugin to version 2.2.1 or later to obtain the patched version. Verify the update does not break existing site functionality.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H

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. Locate JetThemeCore plugin installation
    Search the web server filesystem for the JetThemeCore plugin directory. Common paths include /wp-content/plugins/jetthemecore/ or similar depending on the CMS platform. Verify the plugin folder exists and contains the plugin files.
    Affected if The JetThemeCore plugin folder exists on the server and the plugin is active or installed.
  2. Identify installed JetThemeCore version
    Open the main plugin file (typically plugin.php, index.php, or a similar entry file within the JetThemeCore directory) and locate the version declaration in the file header or a version config file. Compare the version number to 2.2.1.
    Affected if The installed version is lower than 2.2.1 (e.g., 2.2.0, 2.1.x, or earlier).
  3. Check if file handling features are accessible
    Examine the plugin configuration or settings panel in the CMS admin interface. Determine if file upload, import, or download features that handle theme or template files are enabled or accessible to users.
    Affected if File handling features in JetThemeCore are enabled and accessible, particularly theme or template import/export functionality.
  4. Inspect web server access logs
    Review web server access logs (Apache, Nginx, or equivalent) for requests to JetThemeCore endpoints that contain path traversal patterns such as ../, ..\, or absolute paths like /etc/passwd. Search for unusual file access attempts.
    Affected if Logs show requests to JetThemeCore with path traversal sequences accessing files outside the expected upload or content directory.

The environment is affected if the JetThemeCore plugin is installed with a version lower than 2.2.1 and the file handling functionality is accessible to users.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update JetThemeCore plugin to version 2.2.1 or later to obtain the patched version. Verify the update does not break existing site functionality.

Recommended fix Moderate confidence

JetThemeCore version 2.2.1 or later

  1. Create a complete backup of your WordPress site before proceeding with any updates
  2. Navigate to WordPress admin dashboard > Plugins > Installed Plugins
  3. Locate the JetThemeCore plugin by Crocoblock
  4. Update JetThemeCore to version 2.2.1 or later
  5. Verify the update was successful by checking the plugin version number
  6. Test critical site functionality to ensure the update did not break existing features
  7. Clear any caching systems after the update

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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