dbcve.org
UpdraftplusWordPress extension

CVE-2023-32960

MEDIUM · 6.1 CVSS v3.1 Published 2023-06-22
Fix available
A fix is available. Upgrade to after 1.23.3 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in UpdraftPlus.Com, DavidAnderson UpdraftPlus WordPress Backup Plugin <= 1.23.3 versions leads to sitewide Cross-Site Scripting (XSS).

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

CSRF vulnerability in UpdraftPlus WordPress plugin <=1.23.3 allows attackers to trick authenticated administrators into triggering actions that result in stored, sitewide Cross-Site Scripting (XSS). The lack of anti-CSRF tokens in vulnerable endpoints enables attackers to craft malicious requests that inject malicious JavaScript into admin pages or stored settings.

MitigationUpdate UpdraftPlus plugin to version newer than 1.23.3; alternatively, implement anti-CSRF tokens on affected plugin endpoints and consider implementing Content Security Policy (CSP) headers to mitigate XSS impact.

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
UpdraftplusWordPress extension
Affected:<= 1.23.3

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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. Confirm UpdraftPlus plugin is installed
    Log into WordPress admin and navigate to Plugins > Installed Plugins, or inspect /wp-content/plugins/ directory for updraftplus folder
    Affected if UpdraftPlus plugin folder exists in the WordPress installation
  2. Identify installed UpdraftPlus version
    In WordPress admin, go to Plugins > Installed Plugins and find the version number listed under UpdraftPlus plugin description; alternatively, check the version in the plugin's main PHP file header or readme.txt
    Affected if Version displayed is 1.23.3 or any earlier version
  3. Verify plugin is active
    In WordPress admin > Plugins > Installed Plugins, confirm UpdraftPlus shows as 'Active' under the plugin status
    Affected if Plugin is active and running on the site
  4. Assess exposure to social engineering
    Determine if site administrators access the WordPress admin panel and could be tricked into clicking malicious links; this vulnerability requires an authenticated admin to unknowingly submit a crafted request
    Affected if Administrators use the WordPress admin dashboard and could potentially be targeted

If UpdraftPlus version 1.23.3 or earlier is installed, active, and administrators use the WordPress admin panel, the environment is likely affected by this CSRF-to-stored-XSS vulnerability.

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 a release after 1.23.3
Interim mitigation

Update UpdraftPlus plugin to version newer than 1.23.3; alternatively, implement anti-CSRF tokens on affected plugin endpoints and consider implementing Content Security Policy (CSP) headers to mitigate XSS impact.

Recommended fix Moderate confidence

Upgrade to the latest available version of UpdraftPlus (any version above 1.23.3)

  1. 1. Backup your WordPress site before performing any updates
  2. 2. Navigate to the WordPress admin dashboard
  3. 3. Go to Plugins > Installed Plugins
  4. 4. Find UpdraftPlus in the plugin list
  5. 5. If an update is available, click 'Update Now' to upgrade to the latest version
  6. 6. Verify the plugin updated successfully and test backup/restore functionality

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

Fix this in Updraftplus 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-32960 — 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-32960 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