Live › vulnerability › CVE-2026-93953
Go to dashboardThe Backuply WordPress backup plugin up to and including 1.5.8 writes a user's Biographical Info field unescaped into a backup SQL dump, so a crafted value injects SQL when an administrator restores that backup. A subscriber-level account can thereby change the default_role option to administrator and enable open registration, leading to full site takeover.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Sites running the Backuply plugin at version 1.5.8 or earlier where users can edit their Biographical Info field and administrators restore backups created by the plugin. Sites without Backuply installed, or running a newer version, can skip it.
No product ranges from the sources yet.
wp plugin get backuply --field=versiondefault_role and users for unexpected administrator accounts1.5.8 (exact fixed version: unknown)Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-93953")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.