The Duplicator WordPress plugin before 5.1.0, duplicator-pro WordPress plugin before 5.1.0 does not prevent direct
Source GCVE Database
Not known to be exploited : upgrade to 5.1.0 when convenient.
Data as of 4 Nov 2026, 07:29 UTC
Rated Medium 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 steps are indicated.
Description
The Duplicator and duplicator-pro WordPress plugins before version 5.1.0 allow unauthenticated users to directly access certain bundled PHP files. These files initialize without their expected context, causing fatal errors and disclosing server absolute filesystem paths via stack traces.