CVE-2026-1104
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 FastDup – Fastest WordPress Migration & Duplicator plugin for WordPress is vulnerable to unauthorized backup creation and download due to a missing capability check on REST API endpoints in all versions up to, and including, 2.7.1. This makes it possible for authenticated attackers, with Contributor-level access and above, to create and download full-site backup archives containing the entire WordPress installation, including database exports and configuration 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 · high confidenceThe FastDup WordPress plugin lacks proper capability checks on REST API endpoints in versions up to 2.7.1, allowing any authenticated user with Contributor-level access or higher to create and download complete site backups including database exports and configuration files through unprotected API calls.
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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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.
-
Check FastDup plugin versionGo to WordPress admin > Plugins > Installed Plugins > locate FastDup and read the version number displayedAffected if Version is 2.7.1 or earlier
-
Test REST API endpoint authorizationUsing a user account with Contributor role, send a request to the FastDup backup API endpoint (typically /wp-json/fastdup/v1/backup) using curl or browser developer tools. Include the user's authentication cookies or Bearer tokenAffected if The API accepts the request and returns a successful backup creation or download response without returning a 401 or 403 error
-
Review user roles on the siteIn WordPress admin, go to Users > All Users and check for any accounts with Contributor, Author, Editor, or Administrator roles. Also check Settings > General to see if Membership (user registration) is enabledAffected if There are existing users with Contributor-level access or higher, or new user registration is open to the public
-
Inspect for unexpected backup filesCheck the server directory wp-content/uploads/fastdup/ or the plugin's designated backup folder. Use ls -la to list files and their creation timestampsAffected if Backup archives exist that were not created by administrators or that were created at unexpected times
Your environment is affected if FastDup plugin version is 2.7.1 or earlier and any user with Contributor-level access exists on the site, as the vulnerability allows those users to bypass authorization on backup-related REST API endpoints.
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 the FastDup plugin to version 2.7.2 or later which implements proper authorization checks on backup-related REST API endpoints. If immediate update is not possible, consider disabling the plugin or restricting user registrations.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.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 $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1104 — 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-1104 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