dbcve.org
CowidgetsWordPress extension · Codeless

CVE-2024-37419

HIGH · 8.8 CVSS v3.1 Published 2024-07-09
Fix available
A fix is available. Upgrade to 1.2.0 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
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Codeless Cowidgets – Elementor Addons allows Path Traversal.This issue affects Cowidgets – Elementor Addons: from n/a through 1.1.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 Cowidgets – Elementor Addons plugin (versions up to 1.1.1) allows attackers to access files outside the restricted web root directory via '..' sequences in user-controlled path inputs. This is a CWE-22 vulnerability affecting file include/load functionality within the Elementor addon plugin.

MitigationApply vendor patch when available; until then, disable the Cowidgets plugin or restrict access to suspected vulnerable endpoints via web server configuration. Implement input validation that rejects paths containing '..' sequences.

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
CowidgetsWordPress extension
Affected:< 1.2.0

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 Cowidgets plugin is installed
    Check your WordPress plugins directory or admin panel to confirm the Codeless Cowidgets plugin is present and activated
    Affected if The Cowidgets plugin is installed and active in WordPress
  2. Identify installed plugin version
    Check the plugin header file (typically in wp-content/plugins/cowidgets or similar naming) for the Version field, or view it in WordPress plugin admin panel under plugin details
    Affected if The installed version is 1.1.1 or lower (any version below 1.2.0)
  3. Confirm file include/load functionality is accessible
    Review your web server access logs for requests to Cowidgets endpoints that accept path parameters, particularly any that handle file inclusion or loading
    Affected if The plugin file include/load endpoints are accessible and accept user-supplied path inputs
  4. Inspect for path traversal patterns in logs
    Search access logs for '..' sequences in URL parameters or request bodies targeting Cowidgets-related paths
    Affected if Log entries show '..' sequences being passed to plugin parameters, indicating potential exploitation attempts

You are affected if Cowidgets plugin version is below 1.2.0 and its file include/load functionality is accessible to unauthenticated or authenticated 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
Upgrade available Upgrade to 1.2.0 or later
Fixed in 1.2.0
Interim mitigation

Apply vendor patch when available; until then, disable the Cowidgets plugin or restrict access to suspected vulnerable endpoints via web server configuration. Implement input validation that rejects paths containing '..' sequences.

Recommended fix High confidence

1.2.0 or later

  1. 1. Back up your WordPress site database and files before making any changes.
  2. 2. Navigate to the WordPress admin dashboard.
  3. 3. Go to Plugins > Installed Plugins.
  4. 4. Find 'Cowidgets – Elementor Addons' in the plugin list.
  5. 5. If an update is available, click 'Update Now' to upgrade to version 1.2.0 or later.
  6. 6. Alternatively, download Cowidgets version 1.2.0 or newer from the official WordPress plugin repository.
  7. 7. Deactivate and delete the current version, then upload and install the new version.
  8. 8. After update, clear any caching mechanisms.

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

Fix this in Cowidgets 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 the upgrade done

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-37419 — 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-37419 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