dbcve.org
WpcafeWordPress extension · Themewinter

CVE-2024-43135

HIGH · 8.8 CVSS v3.1 Published 2024-08-13
Fix available
A fix is available. Upgrade to 2.2.29 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 PHP Local File Inclusion.This issue affects WPCafe: from n/a through 2.2.28.

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 WPCafe WordPress plugin versions up to 2.2.28 contain a path traversal vulnerability allowing local file inclusion. An attacker can use directory traversal sequences (../) in input parameters to access sensitive files on the server, potentially exposing configuration files, credentials, or executing arbitrary PHP code if the included files are PHP scripts.

MitigationUpdate the WPCafe plugin to the latest version beyond 2.2.28 which should contain the security patch. If no patched version is available, disable the plugin until a fix is released.

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.29

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 version
    In WordPress admin, go to Plugins > Installed Plugins and find WPCafe (by Themewinter). The version number is displayed below the plugin name. Alternatively, check the plugin header in wp-content/plugins/wpcafe/plugin.php for 'Version:' tag.
    Affected if The installed version is any version below 2.2.29 (for example, 2.2.28, 2.2.27, etc.)
  2. Confirm the plugin is active
    In WordPress admin, verify the WPCafe plugin shows as 'Active' in the Plugins list. Path traversal requires the plugin to be loaded for exploitation.
    Affected if The plugin is active and the version is below 2.2.29
  3. Inspect web server access logs for directory traversal attempts
    Review your web server access logs (Apache error.log, Nginx access.log, or similar) for requests containing '../' patterns targeting wp-content or wp-includes paths. Search for patterns like '..%2F' or '..\/'.
    Affected if Log entries show unauthorized attempts to traverse directories using the plugin's endpoints
  4. Check for unauthorized access to sensitive files
    Look for recent file access to wp-config.php, .htaccess, or other configuration files from web server process. Compare file modification timestamps against expected changes.
    Affected if Sensitive configuration files have been accessed or modified after the plugin was installed/updated

You are affected if the WPCafe plugin version is below 2.2.29 and the plugin is active, as the path traversal vulnerability exists in all versions prior to the patch.

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.29 or later
Fixed in 2.2.29
Interim mitigation

Update the WPCafe plugin to the latest version beyond 2.2.28 which should contain the security patch. If no patched version is available, disable the plugin until a fix is released.

Recommended fix High confidence

2.2.29 or later

  1. 1. Back up your WordPress site and database before making any changes
  2. 2. Navigate to the WordPress admin dashboard
  3. 3. Go to Plugins > Installed Plugins
  4. 4. Find the WPCafe plugin in the list
  5. 5. If an update is available, click 'Update Now' to upgrade to the latest version (2.2.29 or higher)
  6. 6. Alternatively, download the latest version from the WordPress plugin repository or Themewinter and upload it manually via Plugins > Add New > Upload Plugin
  7. 7. After updating, verify the plugin is active and functioning correctly
  8. 8. Test that the path traversal vulnerability is no longer exploitable

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

Fix this in Wpcafe Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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