CVE-2023-40004
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 · uneditedMissing Authorization vulnerability in ServMask All-in-One WP Migration Box Extension, ServMask All-in-One WP Migration OneDrive Extension, ServMask All-in-One WP Migration Dropbox Extension, ServMask All-in-One WP Migration Google Drive Extension.This issue affects All-in-One WP Migration Box Extension: from n/a through 1.53; All-in-One WP Migration OneDrive Extension: from n/a through 1.66; All-in-One WP Migration Dropbox Extension: from n/a through 3.75; All-in-One WP Migration Google Drive Extension: from n/a through 2.79.
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 confidenceMultiple All-in-One WP Migration extensions (Box, OneDrive, Dropbox, Google Drive) lack proper authorization checks on certain functions. This allows unauthenticated or lower-privileged users to potentially access sensitive backup operations (download, upload, delete) that should require higher privileges or authentication.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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.
-
Identify installed All-in-One WP Migration extensionsIn WordPress admin, go to Plugins > Installed Plugins and look for 'All-in-One WP Migration' extensions: Box, OneDrive, Dropbox, or Google Drive. Also check the /wp-content/plugins/ directory for folders containing 'ai1wm' or 'all-in-one-wp-migration' with these service names.Affected if Any of the four affected extensions (Box, OneDrive, Dropbox, Google Drive) are installed and activated.
-
Verify WordPress user accounts existIn WordPress admin, go to Users > All Users. Review the list of registered users and their assigned roles.Affected if There are users with roles below Administrator (such as Editor, Author, Contributor, or Subscriber), or the site allows user registration.
-
Confirm backup export functionality is accessibleAttempt to access the plugin's export endpoint via a direct URL request (such as /?ai1wm_export=1 or the specific extension's upload endpoint) without providing admin-level authentication tokens.Affected if The export/download/upload endpoints respond without requiring proper admin-level authorization.
-
Check for unauthenticated access to backup operationsTest accessing the plugin's API endpoints for the cloud storage extensions using a non-logged-in browser session or a low-privilege user account.Affected if Unauthenticated requests or requests from lower-privileged accounts can trigger backup download, upload, or delete operations.
You are affected if any of the four extensions (Box, OneDrive, Dropbox, Google Drive) are installed and the backup operations are accessible to unauthenticated users or accounts with roles below Administrator.
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 all affected extensions to the latest versions which contain proper authorization checks. Until patched, consider disabling these extensions or restricting access via web server-level authentication.
- Consultation2.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-40004 — 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-2023-40004 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