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

- **Severity:** High 8.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **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 available:** No
- **Published:** 16 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-p347-j652-996x

## 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 (Improper Neutralization of Special Elements used in an SQL Command)

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

## Is CVE-2026-93953 being exploited?

There is no known exploitation of CVE-2026-93953 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-93953 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2026-93953 in the wild and no public exploit code.

Affected product: softaculous Backuply – Backup, Restore, Migrate and Clone. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-93953/ (Markdown: https://insights.sbomify.com/CVE-2026-93953/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-93953
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-93953
- OSV: https://osv.dev/vulnerability/CVE-2026-93953

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-93953/
Summaries are generated and may contain mistakes; the official description above is the record.