CVE-2024-47309
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 · uneditedImproper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Condless Cities Shipping Zones for WooCommerce cities-shipping-zones-for-woocommerce allows PHP Local File Inclusion.This issue affects Cities Shipping Zones for WooCommerce: from n/a through <= 1.2.7.
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 confidencePath traversal vulnerability in the Cities Shipping Zones for WooCommerce plugin allows attackers to perform local file inclusion by manipulating file paths, potentially leading to arbitrary PHP code execution on the server.
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
- High
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:H/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 checksWork through these to decide whether this CVE applies to you.
-
Verify the plugin is installedNavigate to WordPress admin > Plugins and look for 'Cities Shipping Zones for WooCommerce' in the installed plugins listAffected if the plugin appears in the installed plugins list
-
Check the installed plugin versionIn WordPress admin > Plugins, click on the plugin details link for 'Cities Shipping Zones for WooCommerce' and note the version number displayedAffected if the installed version has not been patched against path traversal (compare against the vendor's security release notes)
-
Identify if file inclusion endpoints are accessibleCheck the plugin's AJAX handlers or PHP files for code that includes/requires files using user-supplied parameters (look for include(), require(), or similar functions with unsanitized $_GET, $_POST, or $_REQUEST variables)Affected if the plugin contains file inclusion code that uses request parameters without proper sanitization
-
Inspect plugin file permissionsReview the plugin directory permissions on the server file system; list files in wp-content/plugins/cities-shipping-zones-for-woocommerce/ and verify which files are world-readableAffected if the plugin files are readable by the web server process and contain vulnerable code paths
-
Check web server access logsSearch access logs for unusual requests to the plugin directory, specifically looking for patterns like '?file=..' or '../' encoded sequences targeting plugin PHP filesAffected if such path traversal requests have been logged against the plugin endpoints
You are affected if the Cities Shipping Zones for WooCommerce plugin is installed with an unpatched version containing the path traversal vulnerability, and the file inclusion functionality is accessible to unauthenticated users.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpdate to a patched version of the plugin; if unavailable, disable the plugin. Additionally, ensure the web server runs with minimal privileges and restrict file system access.
- Consultation2.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-47309 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-47309 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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