CVE-2026-93953 Backuply <= 1.5.8 - Authenticated (Subscriber+) Second-Order SQL Injection via Restore to Privilege Escalation
Authenticated subscribers can exploit second-order SQL injection in Backuply to escalate privileges to Administrator via backup restore.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- None listed
What is CVE-2026-93953?
CVE-2026-93953 is a high-severity SQL injection vulnerability in softaculous Backuply – Backup, Restore, Migrate and Clone, published on 16 Oct 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Official description
The Backuply – Backup, Restore, Migrate and Clone plugin for WordPress is vulnerable to SQL Injection via the Biographical Info field (second-order, via restore) in all versions up to, and including, 1.5.8 due to insufficient escaping on the user supplied parameter and the lack of sufficient preparation on an existing SQL query. Backuply exports the Biographical Info value verbatim inside an INSERT statement written to the backup's SQL dump (wp_usermeta). When an Administrator later restores such a backup, the crafted payload breaks out of that INSERT statement and appends attacker-controlled SQL that executes with full database privileges. This makes it possible for authenticated attackers, with subscriber-level access and above, to write arbitrary data to the database — in particular to update the default_role option in wp_options to administrator (and enable open user registration) — so that a subsequently registered account is automatically granted the Administrator role, resulting in privilege escalation and full site takeover. Because the injection executes inside an INSERT during restore with no response returned to the attacker, the primitive is used to modify database records rather than to read existing data directly.
Weakness: CWE-89
Which versions are affected by CVE-2026-93953?
How do I fix CVE-2026-93953?
No fix has been published for CVE-2026-93953 yet. Limit exposure of the affected software until one is available.
Use parameterised queries everywhere and never build SQL by joining strings. Upgrade affected software first; a web application firewall only buys time. More about SQL injection.
Is CVE-2026-93953 being exploited?
There is no known exploitation of CVE-2026-93953 in the wild and no public exploit code.
Sources
Also known as GHSA-p347-j652-996x.