Answer in brief
CVE-2026-115262 records a Unknown severity vulnerability in Duplicator < 5.1.0 - Subscriber+ SQLi via Charset and Collation Rewriter During Restore. The current sources do not mark it as known exploited. The current feed maps Unknown/Duplicator (generic), Unknown/duplicator-pro (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Unknown/Duplicator (generic), Unknown/duplicator-pro (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Unknown/Duplicatorgeneric | >=0 <5.1.0 | 5.1.0 |
| Unknown/duplicator-progeneric | >=5.0.0 <5.1.0 | 5.1.0 |
Published upstream
Nov 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 4, 2026
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.
Quoted source text, attributed separately from HOL analysis.