Wc Catalog EnquiryWordPress extension · Wc Marketplace
CVE-2017-18592
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 · uneditedThe woocommerce-catalog-enquiry plugin before 3.1.0 for WordPress has an incorrect wp_upload directory for file uploads.
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 confidenceThe woocommerce-catalog-enquiry plugin before version 3.1.0 for WordPress contains a path traversal vulnerability in its file upload functionality, allowing files to be saved to incorrect directories within the wp_upload folder. This improper directory handling could enable attackers to upload malicious files to accessible locations or access uploaded files in unexpected ways.
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
Wc Catalog EnquiryWordPress extension
< 3.1.0CVSS 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
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
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.
-
Confirm the plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Wc Marketplace Wc Catalog Enquiry' or 'woocommerce-catalog-enquiry'Affected if The plugin appears in the installed plugins list
-
Check the installed plugin versionClick 'View details' on the plugin in the WordPress plugins page, or check the plugin's main PHP file header for the 'Version' tagAffected if The version number is less than 3.1.0 (for example, 3.0.x, 2.x, etc.)
-
Verify file upload functionality is in useNavigate to the plugin settings or any frontend form where customers can submit catalog enquiries, and confirm if a file upload field is present and enabledAffected if File upload fields are available and users can submit files through the plugin
-
Inspect upload directory structureCheck the wp-content/uploads directory for any unexpected subdirectories or files that may have been created via path traversal, looking for directories outside the expected plugin folder structureAffected if Files or directories exist in unexpected locations within wp_upload that suggest path traversal manipulation occurred
You are affected if the Wc Marketplace Wc Catalog Enquiry plugin is installed with a version lower than 3.1.0 and the file upload feature is enabled or has been used.
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 data3.1.0
Update the plugin to version 3.1.0 or later which contains the corrected upload directory path handling, and audit any files uploaded during the vulnerable period for malicious content.
Fix this in Wc Catalog Enquiry
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18592 — 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-2017-18592 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