Quick answers
- Is CVE-2026-115262 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-115262 being exploited in the wild.
- How severe is CVE-2026-115262?
- Informational severity, published 4 November 2026.
- Which products and versions are affected?
- Duplicator before 5.1.0; Duplicator Pro before 5.1.0.
- Is there a fix for CVE-2026-115262?
- Yes: fixed in Duplicator 5.1.0, Duplicator Pro 5.1.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-115262 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-115262?
- Check whether you run Duplicator or Duplicator Pro at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: Duplicator 5.1.0, Duplicator Pro 5.1.0
Technical details
The plugin fails to properly escape or restrict database charset and collation rewriting during backup restore operations. A subscriber can inject SQL by storing a crafted value in their profile, which breaks out of string literals in the restore's INSERT statements when the target server lacks specific charsets or collations. An authenticated attacker with subscriber privilege can execute arbitrary SQL against the restored database.
Affected products
- Duplicator Duplicator before 5.1.0
- Duplicator Duplicator Pro before 5.1.0
Timeline
- 2026-11-02: disclosed
- 2026-11-04: advisory