CVE-2026-5753
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 All-in-One WP Migration Unlimited Extension plugin for WordPress is vulnerable to Missing Authorization in versions up to, and including, 2.83. This is due to the 'Ai1wmve_Schedules_Controller::save' handler for 'admin_post_ai1wm_schedule_event_save' not verifying user capabilities before saving schedule data. This makes it possible for authenticated attackers, with subscriber-level access and above, to create scheduled export jobs and send backup notifications to attacker-controlled email addresses. Because such notifications include the random backup filename, full site backups can subsequently be downloaded from the target site, resulting in sensitive information exposure.
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 All-in-One WP Migration Unlimited Extension plugin fails to verify user capabilities in the 'admin_post_ai1wm_schedule_event_save' action handler, allowing any authenticated user with subscriber-level access to create scheduled backup jobs. Attackers can configure notifications to be sent to attacker-controlled email addresses, which include the randomly-named backup file path, enabling download of complete site backups.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm plugin installationLocate the All-in-One WP Migration Unlimited Extension plugin in wp-content/plugins. Check the main plugin file for the version number in the plugin header comment.Affected if The plugin is installed and its version is below 2.84 (or if version cannot be determined but the plugin is present).
-
Identify the vulnerable handlerLocate the file containing Ai1wmve_Schedules_Controller class. Open the file and locate the 'save' method that handles the 'admin_post_ai1wm_schedule_event_save' action hook.Affected if The save method exists and lacks a current_user_can capability check (such as current_user_can('manage_options')).
-
Verify the action hook registrationSearch the plugin files for 'add_action' registering 'admin_post_ai1wm_schedule_event_save' with the save method as the callback.Affected if The hook is registered without any capability or nonce validation logic preceding it.
-
Inspect scheduled export configurationsCheck the WordPress wp_options table or plugin-specific database tables for records containing ai1wm_schedule. Look for any schedule entries with notification email addresses.Affected if Scheduled export jobs exist and were potentially created by lower-privileged users (subscriber role), or contain unfamiliar email addresses.
-
Review user capabilitiesExamine which user roles have access to the plugin functionality. Check if subscriber-level accounts can access the schedule creation interface or trigger the vulnerable endpoint.Affected if Subscriber or other low-privileged roles have the ability to create or modify scheduled export jobs.
If the plugin is installed, lacks version 2.84 or later, and the save handler does not enforce manage_options capability, the environment is vulnerable to subscriber-level users creating scheduled exports that could expose backup filenames.
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.
dbcve · scopedUpdate the All-in-One WP Migration Unlimited Extension plugin to version 2.84 or later which implements proper capability checks. Review existing scheduled export jobs for unauthorized entries and remove any suspicious email addresses.
Version 2.84 or higher
- Navigate to the WordPress admin dashboard
- Go to Plugins > Installed Plugins
- Locate the All-in-One WP Migration Unlimited Extension plugin
- Check the current version is below 2.84
- Update the plugin to the latest available version (2.84 or higher)
Generated from the published advisory — verify against the referenced sources before acting.
- 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-5753 — 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-5753 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