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.
Published: 2026-10-16
Score: 8 High
EPSS: < 1% Very Low
KEV: No
Impact: Privilege Escalation via Second-Order SQL Injection
Action: Apply vendor patch
AI Analysis

Impact

A second‑order SQL injection flaw exists in the Backuply WordPress plugin in the Biographical Info field that is written verbatim to the backup file. During a later restore, the injected payload breaks out of the INSERT statement and is executed with full database privileges. The attacker can modify entries such as the default_role option in wp_options, elevating a subscriber account to Administrator and enabling automatic administrator registration, leading to a full site takeover.

Affected Systems

Softaculous Backuply plugin for WordPress versions up to and including 1.5.8 is affected.

Risk and Exploitability

The CVSS score is 8, indicating high severity. The EPSS score of < 1% indicates a very low but nonzero exploitation probability, and the vulnerability is not listed in the CISA KEV catalog. The exploit requires an authenticated user with Subscriber level access or higher who can execute a restore operation. Once the restore is performed, the injected SQL runs with database-owner permissions, allowing an attacker to write arbitrary data. Because the attack occurs during a normal restore workflow and produces no direct output, detection is unlikely without monitoring backup files for malicious content.

Generated by OpenCVE AI on October 16, 2026 at 16:18 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Contact the Backuply plugin vendor to obtain the latest update that addresses this vulnerability or check their release notes for a fix.
  • Delete any existing backup files that may contain injected SQL and generate new backups from non‑compromised data.
  • Restrict the restore operation to Administrator users only and validate backup integrity before restoring.

Generated by OpenCVE AI on October 16, 2026 at 16:18 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 16 Oct 2026 15:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Fri, 16 Oct 2026 04:00:00 +0000

Type Values Removed Values Added
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.
Title Backuply <= 1.5.8 - Authenticated (Subscriber+) Second-Order SQL Injection via Restore to Privilege Escalation
Weaknesses CWE-89
References
Metrics cvssV3_1

{'score': 8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: Wordfence

Published:

Updated: 2026-10-16T15:09:41.205Z

Reserved: 2026-09-19T07:03:39.012Z

Link: CVE-2026-93953

cve-icon Vulnrichment

Updated: 2026-10-16T15:00:37.114Z

cve-icon NVD

Status : Deferred

Published: 2026-10-16T04:18:43.143

Modified: 2026-10-16T15:17:36.293

Link: CVE-2026-93953

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-16T16:30:13Z

Weaknesses
  • CWE-89

    Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')