dbcve.org
WpcafeWordPress extension · Themewinter

CVE-2024-37513

HIGH · 8.8 CVSS v3.1 Published 2024-07-09
Fix available
A fix is available. Upgrade to 2.2.28 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 Themewinter WPCafe allows Path Traversal.This issue affects WPCafe: from n/a through 2.2.27.

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 path traversal vulnerability in the Themewinter WPCafe WordPress plugin allows attackers to access files outside the web root directory through manipulation of file path inputs. This could enable unauthorized access to sensitive system files.

MitigationUpdate WPCafe plugin to the latest patched version once available, or implement input validation/sanitization on file path operations to restrict access to allowed directories.

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
WpcafeWordPress extension
Affected:< 2.2.28

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. Locate the WPCafe plugin installation directory
    Access the WordPress plugins folder (wp-content/plugins/) and verify the wpcafe or wpcafe directory exists. Check the main plugin file (e.g., wpcafe.php) for the plugin header which contains the version number.
    Affected if The plugin directory wpcafe or wpcafe is found in the WordPress plugins folder
  2. Determine the installed WPCafe version
    Open the main plugin PHP file and locate the Version field in the plugin header comment block (typically at the top of the file). Alternatively, check the WordPress admin dashboard under Plugins > Installed Plugins and locate WPCafe to view its version.
    Affected if The displayed version number is lower than 2.2.28 (e.g., 2.2.27, 2.2.0, 1.x.x, etc.)
  3. Verify the plugin is active
    Check the WordPress admin under Plugins > Installed Plugins to confirm WPCafe shows as 'Active' rather than 'Inactive' or 'Must-Use'.
    Affected if The plugin is active and running at a version below 2.2.28
  4. Inspect for file path handling endpoints
    Review the plugin source code for PHP files that handle file path operations, particularly look for functions using file_get_contents, fopen, include, require, or similar functions where user-supplied path parameters might be processed. Check for any AJAX endpoints or admin pages that accept file path parameters.
    Affected if The plugin code contains file handling functions that process path inputs without proper sanitization (e.g., ../ sequences) and the plugin is at version < 2.2.28

A user is affected if the WPCafe plugin is installed and active at any version below 2.2.28, as the path traversal vulnerability exists in the plugin's file handling code regardless of specific configuration.

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 2.2.28 or later
Fixed in 2.2.28
Interim mitigation

Update WPCafe plugin to the latest patched version once available, or implement input validation/sanitization on file path operations to restrict access to allowed directories.

Recommended fix High confidence

WPCafe version 2.2.28

  1. Backup your WordPress site before making any changes
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Find the Wpcafe plugin and click Update Now or check for updates
  4. Update Wpcafe to version 2.2.28 or later
  5. Verify the updated version number reflects 2.2.28 or higher in the plugins list

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

Fix this in Wpcafe Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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