CVE-2025-54029
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 extendons WooCommerce csv import export extendons-eo-wooimport-export allows Path Traversal.This issue affects WooCommerce csv import export: from n/a through <= 2.0.6.
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 confidenceA path traversal vulnerability in the extendons-eo-wooimport-export WordPress plugin allows attackers to access files outside the intended directory through manipulation of file path inputs in the CSV import/export functionality.
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
- Changed
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 extendons-eo-wooimport-export plugin is installedNavigate to WordPress admin dashboard > Plugins > Installed Plugins and search for 'extendons-eo-wooimport-export' or 'WooImport Export'. Alternatively, check the /wp-content/plugins/ directory for a folder named 'extendons-eo-wooimport-export'.Affected if The plugin folder exists in the WordPress plugins directory
-
Check the installed plugin versionIn WordPress admin > Plugins > Installed Plugins, find the plugin and note the version number displayed below the plugin name. Compare this to version 2.0.7.Affected if The installed version is lower than 2.0.7 or the version field is empty/unavailable
-
Confirm CSV import/export functionality is accessibleLocate the plugin settings page in WordPress admin (typically under WooCommerce > Import Export or a dedicated Extendons menu). Verify that import/export features are enabled and accessible to users.Affected if The CSV import/export functionality is present and enabled in the plugin settings
-
Check exposure to user rolesReview the plugin settings to determine which WordPress user roles can access the import/export features. Test or inspect whether the functionality is exposed to unauthenticated users, shop managers, or administrators.Affected if The import/export functionality is accessible to users who can upload or process CSV files through the plugin
User is affected if the extendons-eo-wooimport-export plugin is installed with a version lower than 2.0.7 and the CSV import/export feature is accessible.
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 version 2.0.7 or later which patches the path traversal vulnerability. If immediate updating is not possible, implement WAF rules to block directory traversal patterns (../, ..\) and restrict file access controls.
- Consultation3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-54029 — 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-2025-54029 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