dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-0604

MEDIUM · 6.5 CVSS v3.1 Published 2026-01-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
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
The FastDup – Fastest WordPress Migration & Duplicator plugin for WordPress is vulnerable to Path Traversal in all versions up to, and including, 2.7 via the 'dir_path' parameter in the 'njt-fastdup/v1/template/directory-tree' REST API endpoint. This makes it possible for authenticated attackers, with Contributor-level access and above, to read the contents of arbitrary directories on the server, which can contain sensitive information.

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

The FastDup WordPress plugin up to version 2.7 contains a path traversal vulnerability in the REST API endpoint njt-fastdup/v1/template/directory-tree. The dir_path parameter is not properly validated, allowing authenticated users with Contributor-level access to use directory traversal sequences (../) to read arbitrary directories on the server.

MitigationUpgrade to version 2.8 or later which contains the patched version. If immediate upgrade is not possible, implement server-side validation to restrict the dir_path parameter to only allow access within the WordPress uploads directory and block directory traversal sequences.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm FastDup plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'FastDup' in the list, or check the plugin files in wp-content/plugins/ for the njt-fastdup directory
    Affected if FastDup plugin is not installed or the directory does not exist
  2. Identify the installed FastDup version
    In WordPress admin > Plugins, find FastDup and note the version number displayed below the plugin name; alternatively, check the main plugin file (e.g., njt-fastdup/index.php) for the 'Version' header in the plugin comment block
    Affected if The installed version is 2.7 or lower (any version up to and including 2.7)
  3. Verify the vulnerable REST API endpoint exists
    Send a GET request to yoursite.com/wp-json/njt-fastdup/v1/template/directory-tree or check if the route is registered by inspecting the WordPress REST API routes via wp-json/
    Affected if The endpoint responds and accepts a dir_path parameter
  4. Check for existing Contributor-level or higher user accounts
    In WordPress admin > Users, review the user list to identify any accounts with the Contributor, Author, Editor, or Administrator role
    Affected if At least one user account exists with Contributor-level access or higher, enabling them to access the vulnerable endpoint

You are affected if FastDup plugin versions 2.7 or lower are installed and at least one Contributor-level user account exists in WordPress, allowing authenticated access to the vulnerable directory-tree endpoint.

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 to version 2.8 or later which contains the patched version. If immediate upgrade is not possible, implement server-side validation to restrict the dir_path parameter to only allow access within the WordPress uploads directory and block directory traversal sequences.

Recommended fix Moderate confidence

Latest version available in WordPress plugin repository (version 2.8 or higher)

  1. 1. Identify the current installed version of the FastDup plugin in your WordPress installation
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. 3. Locate 'FastDup – Fastest WordPress Migration & Duplicator' and check the version number
  4. 4. If the installed version is 2.7 or lower, update to the latest available version from the WordPress plugin repository
  5. 5. After updating, verify the plugin version in the plugins list to confirm the update was successful
  6. 6. Test that the FastDup functionality still works as expected after the update

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-0604 — 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-2026-0604 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