dbcve.org
Checkout Field Editor For WoocommerceWordPress extension · Themehigh

CVE-2024-35658

CRITICAL · 9.1 CVSS v3.1 Published 2024-06-10
Fix available
A fix is available. Upgrade to 3.6.3 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 Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in ThemeHigh Checkout Field Editor for WooCommerce (Pro) allows Functionality Misuse, File Manipulation.This issue affects Checkout Field Editor for WooCommerce (Pro): from n/a through 3.6.2.

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 ThemeHigh Checkout Field Editor for WooCommerce Pro (versions up to 3.6.2) allows attackers to manipulate file paths using '../' sequences to access files outside restricted directories. The vulnerability enables functionality misuse and arbitrary file manipulation through insufficient input validation on file path parameters.

MitigationUpgrade to the latest version of Checkout Field Editor Pro. If no patch is available, disable the plugin until a fix is released. Review and sanitize all file path parameters in the plugin to prevent directory traversal.

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
Checkout Field Editor For WoocommerceWordPress extension
Affected:< 3.6.3

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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. Identify if the plugin is installed
    Check your WordPress site's wp-content/plugins/ directory for the 'checkout-field-editor-for-woocommerce' or 'checkout-field-editor-for-woocommerce-pro' folder, or view the installed plugins list in WordPress admin under Plugins
    Affected if The ThemeHigh Checkout Field Editor plugin is present in the WordPress installation
  2. Determine the installed version
    In WordPress admin, go to Plugins > Installed Plugins and locate the Checkout Field Editor entry. The version number is displayed beneath the plugin name. Alternatively, check the main plugin PHP file for a 'Version' header comment
    Affected if The displayed version is lower than 3.6.3 (for example, 3.6.2, 3.6.1, 3.5.x, etc.)
  3. Verify file path handling is accessible
    Check if the plugin's file upload, export, import, or backup features are enabled. These are typically found in WooCommerce > Checkout Form > any tab with file operations, or in the plugin settings panel
    Affected if Any file-related functionality (file uploads, export/import of checkout fields, backup features) is active on the site
  4. Inspect server access logs for path traversal patterns
    Review web server access logs (Apache, Nginx, or reverse proxy) for requests to the plugin endpoints containing '../' sequences or unusual file path references. Look for patterns like '..%2F' or multiple consecutive dot-slash sequences
    Affected if Log entries show attempted or successful traversal patterns targeting plugin AJAX handlers or file processing endpoints

A site is affected if it has ThemeHigh Checkout Field Editor for WooCommerce installed with a version below 3.6.3 and has file-related plugin features accessible to 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 3.6.3 or later
Fixed in 3.6.3
Interim mitigation

Upgrade to the latest version of Checkout Field Editor Pro. If no patch is available, disable the plugin until a fix is released. Review and sanitize all file path parameters in the plugin to prevent directory traversal.

Recommended fix High confidence

3.6.3

  1. Backup your WordPress site and database before making any changes
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Find 'Checkout Field Editor for WooCommerce' (or 'Checkout Field Editor for WooCommerce Pro')
  4. Click 'Update now' if an update is available, or manually download version 3.6.3 from the WordPress plugin repository and upload it
  5. Verify the plugin version is now 3.6.3 under Plugins > Installed Plugins
  6. Test checkout functionality to ensure the plugin is working correctly after the update

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

Fix this in Checkout Field Editor For Woocommerce Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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