dbcve.org
JetelementsWordPress extension · Crocoblock

CVE-2024-7145

HIGH · 8.8 CVSS v3.1 Published 2024-08-16
Fix available
A fix is available. Upgrade to after 2.6.20 or later.
See remediation →
94/100
Remediation priority · Urgent
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
The JetElements plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 2.6.20 via the 'progress_type' parameter. This makes it possible for authenticated attackers, with Contributor-level access and above, to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other “safe” file types can be uploaded and included.

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 JetElements WordPress plugin versions up to 2.6.20 contain a Local File Inclusion vulnerability via the 'progress_type' parameter. Authenticated attackers with Contributor-level access or higher can include and execute arbitrary files on the server, enabling PHP code execution to bypass access controls or obtain sensitive data.

MitigationUpdate JetElements plugin to version 2.6.21 or later to patch the LFI vulnerability. Until patched, consider restricting user permissions or temporarily disabling the plugin.

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
JetelementsWordPress extension
Affected:<= 2.6.20

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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. Verify JetElements plugin is installed
    Navigate to WordPress Admin > Plugins and look for 'JetElements' by Crocoblock in the installed plugins list
    Affected if JetElements plugin appears in the plugins list
  2. Check installed JetElements version
    In WordPress Admin > Plugins, find JetElements and note the version number displayed under the plugin name
    Affected if The version shown is 2.6.20 or lower
  3. Identify users with Contributor-level access or higher
    Go to WordPress Admin > Users and review the role assigned to each user account. Contributor, Author, Editor, and Administrator roles all have access at or above the Contributor level
    Affected if Any user account has a role of Contributor, Author, Editor, or Administrator and the plugin version is 2.6.20 or lower
  4. Verify the vulnerable progress_type parameter is present
    Inspect AJAX requests or frontend elements that utilize JetElements widgets, specifically looking for any functionality that references a 'progress_type' parameter in the codebase or network requests
    Affected if The plugin handles a 'progress_type' parameter and the installed version is 2.6.20 or lower

The environment is affected if the JetElements plugin is installed at version 2.6.20 or lower AND any user account has Contributor-level access or higher, allowing exploitation of the progress_type parameter for local file inclusion.

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 a release after 2.6.20
Interim mitigation

Update JetElements plugin to version 2.6.21 or later to patch the LFI vulnerability. Until patched, consider restricting user permissions or temporarily disabling the plugin.

Recommended fix Moderate confidence

A version higher than 2.6.20 (check crocoblock.com for the latest stable release)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find JetElements in the plugin list
  4. Check the current version number to confirm it is 2.6.20 or earlier
  5. If an update is available, click 'Update Now' to install the latest version
  6. If no update appears, navigate to Plugins > Add New > Upload Plugin and upload the latest version from the official JetElements provider (Crocoblock)
  7. After updating, verify the new version number reflects a version higher than 2.6.20

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

Fix this in Jetelements Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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