The Duplicator WordPress plugin before 5.1.0, duplicator-pro WordPress plugin before 5.1.0 does not restrict its
Source GCVE Database
Not known to be exploited : upgrade to 5.1.0 soon.
Data as of 4 Nov 2026, 07:30 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 5.1.0
Exploitation evidence
Disclosed: evidence found.
CVE published 4 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 3 Nov 2026.
What to do
Upgrade Duplicator and duplicator-pro to 5.1.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Duplicator | Affected
| Fixed in
|
| duplicator-pro | Affected
| Fixed in
|
AI-suggested
Upgrade the Duplicator and duplicator-pro WordPress plugins to version 5.1.0 or later where this issue is fixed. No other mitigation is indicated in the provided data.
Description
The Duplicator and duplicator-pro WordPress plugins before version 5.1.0 have a vulnerability where the database charset and collation rewrite during a restore operation is not properly restricted to schema statements. This flaw allows a Subscriber user to inject SQL code into the restore's INSERT statement by storing crafted values in their profile, potentially leading to SQL injection when an administrator restores a backup on a server missing certain charsets or collations.