dbcve.org
FastdupWordPress extension · Ninjateam

CVE-2023-6592

MEDIUM · 5.3 CVSS v3.1 Published 2024-01-16
Fix available
A fix is available. Upgrade to 2.2 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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 WordPress plugin before 2.2 does not prevent directory listing in sensitive directories containing export files.

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 confidence

The FastDup WordPress plugin before version 2.2 fails to disable directory listing in sensitive directories that contain export files. This allows unauthenticated attackers to enumerate files in these directories, potentially exposing sensitive exported data through directory browsing.

MitigationUpgrade FastDup plugin to version 2.2 or later, and ensure proper access controls (index.php files or .htaccess rules) are in place for any directories containing export files to prevent directory listing.

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
FastdupWordPress extension
Affected:< 2.2

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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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. Check FastDup plugin version
    In WordPress admin, go to Plugins > Installed Plugins and find Ninjateam FastDup. Alternatively, check the plugin main file (wp-content/plugins/fastdup/fastdup.php) for the 'Version' header comment, or query the WordPress database: SELECT option_value FROM wp_options WHERE option_name = 'active_plugins' and check the plugin version via file system.
    Affected if The installed version is less than 2.2
  2. Identify FastDup export directories
    Search the wp-content/uploads/ directory for directories named 'fastdup-export' or similar export folders. Check common paths like wp-content/uploads/fastdup/, wp-content/fastdup-exports/, or directories with 'export', 'backup', or 'dump' in the name created by FastDup.
    Affected if Export directories exist and contain exported data files
  3. Check for index.php in export directories
    For each identified export directory, verify if an index.php file exists inside it: ls -la /path/to/export/directory/ or dir /path\to\export\directory\. If no index.php (or blank index.php) exists, directory listing may be enabled.
    Affected if No index.php file or an empty index.php file is present in export directories
  4. Verify directory listing is enabled
    Attempt to access the export directory via HTTP (e.g., https://yoursite.com/wp-content/uploads/fastdup-export/). If the web server returns a directory listing showing files rather than an index page or 403/404 error, directory listing is enabled.
    Affected if Directory listing is accessible and shows file contents

You are affected if FastDup version is below 2.2 AND export directories exist without proper index.php protection, allowing unauthenticated directory browsing.

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
Upgrade available Upgrade to 2.2 or later
Fixed in 2.2
Interim mitigation

Upgrade FastDup plugin to version 2.2 or later, and ensure proper access controls (index.php files or .htaccess rules) are in place for any directories containing export files to prevent directory listing.

Recommended fix Moderate confidence

FastDup version 2.2

  1. Backup your WordPress site before making any changes
  2. Update the FastDup plugin to version 2.2 or later through the WordPress plugin repository or your plugin management system
  3. After updating, verify that directory listing is now prevented in the export directories by attempting to access an export directory directly
  4. Confirm that sensitive export files are no longer publicly accessible via directory listing

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

Fix this in Fastdup Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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