CVE-2026-25328
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 add-ons.org Product File Upload for WooCommerce products-file-upload-for-woocommerce allows Path Traversal.This issue affects Product File Upload for WooCommerce: from n/a through <= 2.2.4.
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 Product File Upload for WooCommerce plugin <= 2.2.4 contains a path traversal vulnerability in its file upload functionality. An attacker could potentially use directory traversal sequences (e.g., ../../../) in uploaded filenames to write files outside the intended upload directory, potentially achieving arbitrary file write or overwrite 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
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:N/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 installedLog into WordPress admin and navigate to Plugins > Installed Plugins, or check the /wp-content/plugins/ directory for a folder named 'product-file-upload-for-woocommerce' or similarAffected if the plugin folder exists in the WordPress plugins directory
-
Check the installed versionIn WordPress admin, find Product File Upload for WooCommerce in the plugins list and view the version number displayed, or open the main plugin PHP file and look for the 'Version' header in the plugin commentsAffected if the displayed version is 2.2.4 or any lower version number
-
Confirm file upload functionality is activeCheck WooCommerce product settings to see if the file upload feature is enabled for any product type, or review the plugin's configuration options in WooCommerce > SettingsAffected if the file upload feature is enabled or configured for products
-
Inspect upload handling for path traversal exposureIf possible, review the plugin's upload handler code (typically in the main plugin PHP file or an includes/upload.php file) for any file_put_contents, move_uploaded_file, or similar functions that process the uploaded filename without sanitizing directory traversal sequencesAffected if the code processes uploaded file names without validating or stripping ../ sequences
You are affected if Product File Upload for WooCommerce is installed with version 2.2.4 or lower and the file upload feature is enabled, as this combination allows path traversal in filenames to write files outside the intended directory.
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 dataUpgrade to a patched version of Product File Upload for WooCommerce that addresses the path traversal vulnerability. If no patch is available, consider disabling the file upload functionality until a fix is released, and implement server-side web application firewall rules to detect and block path traversal patterns in upload requests.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-25328 — 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-2026-25328 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