dbcve.org
Updraftplus ExtensionWordPress extension · Mainwp

CVE-2023-23640

HIGH · 8.8 CVSS v3.1 Published 2024-06-09
Fix available
A fix is available. Upgrade to 4.0.7 or later.
See remediation →
94/100
Remediation priority · Urgent
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
Missing Authorization vulnerability in MainWP MainWP UpdraftPlus Extension.This issue affects MainWP UpdraftPlus Extension: from n/a through 4.0.6.

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

This is a Missing Authorization (CWE-862) vulnerability in the MainWP UpdraftPlus Extension where the plugin fails to properly verify user permissions before allowing certain actions. An attacker with network access and some level of user authentication could potentially perform unauthorized operations, likely related to backup management functions, without proper capability checks.

MitigationUpdate the MainWP UpdraftPlus Extension to a version newer than 4.0.6 when available. If no patch exists, implement proper WordPress capability checks and nonce verification on all sensitive actions within the plugin.

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
Updraftplus ExtensionWordPress extension
Affected:< 4.0.7

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 checks

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

  1. Check if MainWP UpdraftPlus Extension is installed
    Navigate to WordPress admin > Plugins > Installed Plugins and look for 'MainWP UpdraftPlus Extension' or check the plugin files in wp-content/plugins/ for the MainWP UpdraftPlus directory
    Affected if The plugin is not found in the installed plugins list
  2. Identify the installed version number
    In the WordPress plugins admin page, locate the MainWP UpdraftPlus Extension and view the version number displayed beneath the plugin name, or open the main plugin PHP file and look for the 'Version' header in the plugin comment block
    Affected if Version number is less than 4.0.7 or cannot be determined
  3. Verify the plugin is active
    In WordPress admin > Plugins > Installed Plugins, confirm that MainWP UpdraftPlus Extension shows as 'Active' rather than 'Inactive' or 'Not Activated'
    Affected if The plugin is currently activated and running on the site
  4. Confirm backup-related functions are accessible
    Check if the MainWP dashboard shows backup management options from the UpdraftPlus extension, which would indicate the vulnerable functionality is enabled and reachable
    Affected if The backup management interface is accessible through the MainWP dashboard

The environment is affected if MainWP UpdraftPlus Extension version 4.0.6 or lower is installed and actively running on the WordPress site.

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 4.0.7 or later
Fixed in 4.0.7
Interim mitigation

Update the MainWP UpdraftPlus Extension to a version newer than 4.0.6 when available. If no patch exists, implement proper WordPress capability checks and nonce verification on all sensitive actions within the plugin.

Recommended fix Moderate confidence

4.0.7

  1. 1. Log in to your WordPress admin dashboard
  2. 2. Navigate to the Plugins section
  3. 3. Find the MainWP UpdraftPlus Extension plugin
  4. 4. Check the current version - if it is 4.0.6 or earlier, an update is needed
  5. 5. Update the plugin to version 4.0.7 or latest available version
  6. 6. Verify the update completed successfully
  7. 7. Test that the UpdraftPlus extension functionality works correctly in MainWP

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

Fix this in Updraftplus Extension Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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