dbcve.org
Path TraversalWeakness · CWE-22

CVE-2023-35881

HIGH · 7.6 CVSS v3.1 Published 2024-05-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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 WooCommerce WooCommerce One Page Checkout allows PHP Local File Inclusion.This issue affects WooCommerce One Page Checkout: from n/a through 2.3.0.

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

A path traversal vulnerability in the WooCommerce One Page Checkout plugin versions up to 2.3.0 allows unauthenticated attackers to manipulate file path references to include arbitrary local PHP files on the server, potentially exposing sensitive configuration data or enabling code execution.

MitigationUpgrade WooCommerce One Page Checkout to version 2.3.1 or later. If immediate patching is not possible, restrict web server access to the plugin directory and disable any vulnerable endpoint handlers.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L

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 installed plugin version
    Locate the WooCommerce One Page Checkout plugin directory (wp-content/plugins/woocommerce-one-page-checkout/) and open the main plugin file (usually one-page-checkout.php or similar). Look for the 'Version:' header comment or a $version variable definition.
    Affected if The version listed is 2.3.0 or lower (any version up to and including 2.3.0).
  2. Verify One Page Checkout functionality is active
    Log into the WordPress admin dashboard and navigate to WooCommerce > Settings > One Page Checkout. Check whether the module is enabled or if any One Page Checkout shortcodes are in use on the site.
    Affected if The One Page Checkout feature is enabled or shortcodes like [one_page_checkout] are present on live pages.
  3. Inspect checkout ajax handlers for path traversal patterns
    Examine the plugin PHP files in the includes/ or templates/ directories for code that uses include, require, or similar functions with user-controlled input. Look for patterns where $_GET, $_POST, or $_REQUEST parameters are used to build file paths without proper sanitization (checking for ../ sequences).
    Affected if Code exists that accepts file path parameters from requests and includes them without validating that the path stays within an allowed directory.
  4. Check for exposed vulnerable endpoints
    Review the plugin's main file for registered ajax actions (add_action('wp_ajax_...')) or rewrite rules that handle checkout requests. Identify URLs like /wp-admin/admin-ajax.php?action=... that may pass file path arguments.
    Affected if The plugin exposes an unauthenticated ajax endpoint (wp_ajax_nopriv_...) that accepts file path parameters used in include/require statements.

You are affected if the installed plugin version is 2.3.0 or earlier AND the One Page Checkout module is enabled with a vulnerable path-handling endpoint accessible to unauthenticated 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade WooCommerce One Page Checkout to version 2.3.1 or later. If immediate patching is not possible, restrict web server access to the plugin directory and disable any vulnerable endpoint handlers.

Recommended fix Moderate confidence

Latest version available in WordPress plugin repository (newer than 2.3.0)

  1. 1. Identify the currently installed version of the WooCommerce One Page Checkout plugin
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. 3. Locate the WooCommerce One Page Checkout plugin
  4. 4. If the installed version is 2.3.0 or lower, update to the latest available version from the WordPress plugin repository
  5. 5. Alternatively, navigate to Dashboard > Updates to check for and apply available updates
  6. 6. Verify the update was successful and test the One Page Checkout functionality

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

Have this fixed 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 help mitigating

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-2023-35881 — 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-2023-35881 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