dbcve.org
Cryptocurrency Widgets For ElementorWordPress extension · Coolplugins

CVE-2024-53739

CRITICAL · 9.8 CVSS v3.1 Published 2024-11-30
Fix available
A fix is available. Upgrade to 1.6.5 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Cool Plugins Cryptocurrency Widgets For Elementor cryptocurrency-widgets-for-elementor allows PHP Local File Inclusion.This issue affects Cryptocurrency Widgets For Elementor: from n/a through <= 1.6.4.

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

A Local File Inclusion (LFI) vulnerability in the Cryptocurrency Widgets For Elementor WordPress plugin (versions up to 1.6.4) allows attackers to include and execute arbitrary local PHP files due to improper control of filename parameters in include/require statements. This can lead to disclosure of sensitive configuration files, credentials, or potentially remote code execution depending on server configuration.

MitigationUpdate Cryptocurrency Widgets For Elementor to the latest patched version immediately. If no patched version is available, deactivate and remove the plugin until a fix is released. Implement web application firewall rules to block directory traversal patterns (e.g., ../) as a temporary mitigation.

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
Cryptocurrency Widgets For ElementorWordPress extension
Affected:< 1.6.5

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Confirm the plugin is installed
    Locate the plugin directory at /wp-content/plugins/ and check for a folder named 'cryptocurrency-widgets-for-elementor' or 'coolplugins-cryptocurrency-widgets-for-elementor'. Alternatively, query the WordPress database in the wp_options table for option_name='active_plugins' to see if the plugin is activated.
    Affected if The plugin folder exists in the WordPress plugins directory or the plugin is listed as active in the WordPress database.
  2. Identify the installed version
    Open the main plugin PHP file (typically cryptowidgets-for-elementor.php or similar in the plugin folder) and read the version header: look for 'Version: X.X.X' in the file comments at the top. Alternatively, query wp_options table for option_name containing the plugin version.
    Affected if The version returned is less than 1.6.5 (for example, 1.6.4, 1.6.3, etc.).
  3. Verify the LFI vulnerability is accessible
    Examine the plugin source code for PHP files containing include, require, include_once, or require_once statements that use variables as file paths without sanitization (such as $_GET, $_POST, or $_REQUEST parameters). Search for patterns like 'include($_REQUEST[', 'require($_GET[', or similar unsanitized file inclusions.
    Affected if The plugin code contains include/require statements that directly use request parameters as file paths without validation, and these endpoints are reachable via HTTP without requiring authentication or with standard WordPress user privileges.
  4. Check for exposed vulnerable parameters
    Review the plugin's AJAX handlers (usually in files with 'ajax' in the name or hooks like 'wp_ajax_') and any direct-access PHP files to identify which parameters are passed to the vulnerable include/require statements. Test accessing these endpoints with a crafted parameter value like '../../../../../../etc/passwd' to confirm the LFI behavior.
    Affected if The vulnerable parameters are reachable via HTTP requests and the server responds with content from the requested file path, confirming the LFI is exploitable.

The environment is affected if the Cryptocurrency Widgets for Elementor plugin is installed with a version lower than 1.6.5 and contains the unsanitized file inclusion vulnerability that is accessible via HTTP requests.

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.6.5 or later
Fixed in 1.6.5
Interim mitigation

Update Cryptocurrency Widgets For Elementor to the latest patched version immediately. If no patched version is available, deactivate and remove the plugin until a fix is released. Implement web application firewall rules to block directory traversal patterns (e.g., ../) as a temporary mitigation.

Recommended fix Moderate confidence

1.6.5

  1. Log in to your WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Cryptocurrency Widgets For Elementor' in the plugin list
  4. If an update is available, click 'Update Now' to upgrade to version 1.6.5 or higher
  5. Alternatively, download version 1.6.5 from the WordPress plugin repository and upload it manually via Plugins > Add New > Upload Plugin
  6. After updating, verify the installed version is 1.6.5 or later

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

Fix this in Cryptocurrency Widgets For Elementor Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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