dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2023-51681

MEDIUM · 6.5 CVSS v3.1 Published 2024-02-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/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 Duplicator Duplicator – WordPress Migration & Backup Plugin.This issue affects Duplicator – WordPress Migration & Backup Plugin: from n/a through 1.5.7.

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 · moderate confidence

Cross-Site Request Forgery (CSRF) vulnerability in the Duplicator WordPress plugin versions through 1.5.7 allows attackers to induce authenticated administrators to perform unintended actions by tricking them into visiting malicious pages or clicking links while logged in.

MitigationImplement anti-CSRF tokens (nonces) for state-changing operations and verify request origins via Referer header checks or SameSite cookie attributes to prevent forged requests.

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
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/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. Locate Duplicator plugin installation
    Access WordPress admin dashboard, navigate to Plugins > Installed Plugins, or inspect the /wp-content/plugins/duplicator/ directory via file system
    Affected if Duplicator plugin directory exists in the WordPress installation
  2. Identify installed Duplicator version
    In WordPress admin, go to Plugins > Installed Plugins and find the Duplicator plugin - the version number is displayed below the plugin name. Alternatively, check the main plugin file (e.g., duplicator.php) for the 'Version' header comment
    Affected if Version is 1.5.7 or any version 'through' 1.5.7 (including earlier versions like 1.5.6, 1.5.5, etc.)
  3. Confirm plugin is active
    In WordPress admin under Plugins > Installed Plugins, verify the Duplicator plugin shows as 'Active' (not just installed but not activated)
    Affected if Plugin is currently active on the WordPress site
  4. Verify administrative user sessions exist
    Review WordPress user list under Users > All Users to confirm administrator-level accounts exist. CSRF requires an authenticated administrator to unknowingly submit a forged request
    Affected if At least one user with Administrator role exists and is logged into the site

You are affected if the Duplicator plugin versions through 1.5.7 is installed and active on your WordPress site, allowing forged requests to be executed when an administrator is tricked into visiting a malicious page while logged in.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement anti-CSRF tokens (nonces) for state-changing operations and verify request origins via Referer header checks or SameSite cookie attributes to prevent forged requests.

Recommended fix Moderate confidence

1.5.8 or later

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Duplicator – WordPress Migration & Backup Plugin'
  4. Click 'Update now' if an update is available, or click on the plugin name and select 'Update'
  5. Verify the update completes successfully
  6. Confirm the plugin version is 1.5.8 or later

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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