Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain Subscriber account on source site
-
DeliveryStore crafted SQL payload in own profile field
-
ExploitAdministrator backs up and restores onto charset/collation-mismatched server
-
ExecutionPayload breaks out of string literal in restore INSERT
-
ImpactInject and execute SQL against restored database
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires a specific chain rather than a default remote attack: (1) the attacker needs a low-privilege authenticated Subscriber account on the source site so they can store a malicious value in their own profile; (2) a site administrator must subsequently create a backup and perform a restore (the required user interaction); and (3) the destination server must lack one of the source server's charsets or collations, which is what causes the plugin's charset/collation rewrite to wrongly extend beyond schema statements into the INSERT statement. The vulnerability affects Duplicator (free) before 5.1.0 and Duplicator Pro 5.0.0 before 5.1.0. Limiting factors: authenticated Subscriber access, mandatory admin restore action, and the non-attacker-controlled charset/collation mismatch together make opportunistic or automated exploitation unlikely (reflected in SSVC Automatable: no and high attack complexity). |
| Impact | This is a genuine but comparatively low-priority issue, and the signals are internally consistent rather than conflicting. The CVSS 3.1 base score is 4.8 (medium) with vector AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:H/A:N: network-reachable but gated by high attack complexity, low-privilege (authenticated Subscriber) access, and required user interaction by an administrator. EPSS is very low at 0.16% (6th percentile), and CISA SSVC reports Exploitation: none, Automatable: no, Technical Impact: partial - all of which agree that this is not a mass-exploitable, drive-by flaw. It is not listed in CISA KEV, so there is no public evidence of active exploitation. A public PoC reference exists (WPScan); it is not verified as working exploit code. The vendor's priority label is 'this_month', not act_now/emergency, which matches the picture: a real integrity-affecting SQL injection worth patching on a normal cadence, not an incident-response emergency. The AC:H and UI:R metrics are well justified by the description - exploitation depends on an administrator restoring a backup onto a server that happens to lack one of the source's charsets/collations - so the raw network vector overstates practical reachability. |
| Exploit ScenarioDerived | An attacker registers or already holds a low-privilege Subscriber account and stores a crafted value in their own profile that is designed to break out of a SQL string literal. When a site administrator later takes a backup and restores it onto a server missing one of the source's charsets or collations, the plugin's charset/collation rewrite misapplies to the INSERT statement and the attacker's profile value injects SQL during the restore. A public PoC reference exists but is not verified as working exploit code, and exploitation depends on the administrator-driven restore plus the charset mismatch. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Nov 04, 2026
SQL injection in the Duplicator (free) and Duplicator Pro WordPress plugins before 5.1.0 allows an authenticated Subscriber to plant a crafted value in their own user profile that breaks out of its string literal and is injected into the restore's INSERT statement. The flaw is only reachable through a specific chain: an administrator must create a backup and later restore it onto a server that lacks one of the source server's charsets or collations, which is the condition that causes the plugin's charset/collation rewrite to spill past schema statements into data statements (CVSS 4.8, AC:H/PR:L/UI:R, integrity-only impact). No confirmed working exploit code is known - a public PoC reference exists but is not verified as working exploit code, CISA SSVC records exploitation as none and automatable as no, and EPSS is very low at 0.16% (6th percentile), so this is a this-month priority rather than an emergency.
RemediationAI
Upgrade to Duplicator 5.1.0 or later, and to Duplicator Pro 5.1.0 or later - 5.1.0 is the first release that restricts the charset and collation rewrite to schema statements - following the vendor advisory at https://wpscan.com/vulnerability/5359cd4c-9867-4b33-b0b2-ca85819f9af4/. If an immediate upgrade is not possible, the exposure can be reduced by removing the three preconditions: ensure the destination server supports every charset and collation present on the source server before running a restore, so the rewrite path is never entered (cost: requires verifying and aligning server charsets/collations beforehand); keep open Subscriber registration closed or audit existing Subscriber profile fields for crafted values before taking a backup (cost: operational overhead and does not protect sites that legitimately allow self-registration); and avoid restoring untrusted third-party backups. These measures lower risk but do not replace the 5.1.0 update, which is the complete vendor fix.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 2 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The Duplicator plugins perform full WordPress site backup and migration, serializing the database into a dump and replaying it during restore. To make a dump portable, the restore routine rewrites charset and collation declarations where the destination MySQL/MariaDB server does not support the source server's charsets or collations. That rewriting is not scoped strictly to schema statements (CREATE TABLE and similar), so it also reaches the INSERT statements used to repopulate tables such as the users table. A Subscriber's own profile fields are attacker-controlled input that is stored and later serialized into the dump; by placing a value crafted to terminate its string literal, the Subscriber can have arbitrary SQL spliced into the restore-time INSERT statement. The root cause class is CWE-89 (SQL injection), and the practical consequence is that attacker-chosen rows or values land in the restored database, giving integrity impact while confidentiality and availability are assessed as unaffected. Per the affected CPE data, both the free Duplicator plugin and Duplicator Pro are in scope, with the vendor attribution recorded as unknown in the CPE strings.
Know when Duplicator gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:H/A:N
Subscriber account needed (PR:L), admin restore is required interaction (UI:R), success depends on a charset/collation mismatch outside attacker control (AC:H); SQL injection into the restore corrupts the database (I:H).
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
3DescriptionCVE.org
The Duplicator WordPress plugin before 5.1.0, duplicator-pro WordPress plugin before 5.1.0 does not restrict its database charset and collation rewrite to schema statements during a restore, so a value a Subscriber stores in their own profile can break out of its string literal and inject SQL into the restore's INSERT statement when an administrator restores the backup onto a server lacking one of the source's charsets or collations.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.
More in Duplicator
View allAn issue was discovered in Snap Creek Duplicator before 1.2.42. Rated critical severity (CVSS 9.8), this vulnerability i
The Duplicator WordPress plugin before 1.3.0 does not properly escape values when its installer script replaces values i
The Duplicator plugin in Wordpress before 0.5.10 allows remote authenticated users to create and download backup files.
The Duplicator WordPress plugin before 1.5.7.1, Duplicator Pro WordPress plugin before 4.5.14.2 does not disallow listin
The Duplicator WordPress plugin before 1.4.7 discloses the url of the a backup to unauthenticated visitors accessing the
The Snap Creek Duplicator plugin before 1.3.28 for WordPress (and Duplicator Pro before 3.8.7.1) allows Directory Traver
Privilege escalation in the Duplicator WordPress plugin before 5.0.0 lets an administrator of a WordPress Multisite chil
Cross-site scripting (XSS) vulnerability in installer/build/view.step4.php of the SnapCreek Duplicator plugin 1.2.32 for
Reflected cross-site scripting in Duplicator and Duplicator Pro WordPress plugins before 5.1.0 lets an attacker run scri
Cross-site scripting (XSS) vulnerability in files/installer.cleanup.php in the Duplicator plugin before 0.4.5 for WordPr
Unauthenticated remote attackers can disclose a WordPress server's absolute filesystem paths by directly requesting PHP
The Duplicator WordPress plugin before 1.4.7 does not authenticate or authorize visitors before displaying information a
EUVD-2026-116730
GHSA-8p5f-q54f-ww8c
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB