Backuply WordPress Plugin Vulnerability Risks Site Takeover

A second-order SQL injection vulnerability allows subscribers to escalate access to administrator on 600,000 sites.

Updated on Oct. 15, 2026 in Cybersecurity

Bold flat-color editorial illustration featuring a geometric steel padlock clamped onto a data-center rail, symbolizing digital security and vulnerability.
Security researchers discovered a critical privilege-escalation vulnerability in the Backuply WordPress plugin affecting over 600,000 active websites worldwide. AI Illustration. Upload story photo >

Live Poll

Do you trust the third-party plugins you use to keep your website secure from attacks?

Security researchers identified a second-order SQL injection vulnerability in the Backuply WordPress plugin on September 17, 2026. This flaw allows authenticated attackers with subscriber-level access to escalate their privileges to administrator status and compromise affected sites.

Why it matters

The vulnerability affects more than 600,000 active installations of the Backuply plugin, creating a significant security risk for a large portion of the WordPress ecosystem. Attackers can gain complete site control by exploiting the way the plugin handles database backup restorations.

The vulnerability involves a second-order SQL injection, where malicious input is stored by the system and executed later during a database backup restoration. This sequence grants an attacker administrative-level access, far exceeding their original subscriber-level permissions.

The players

Backuply

A WordPress plugin used for site backup and restoration, currently installed on more than 600,000 active sites.

WordPress

A popular content management system that hosts a wide ecosystem of plugins, including those prone to server-side vulnerabilities.

The details

A second-order SQL injection occurs when a web application takes user-supplied data and stores it in a database without proper sanitization. In the case of Backuply, an attacker with subscriber-level access submits a malicious payload that remains dormant until the plugin triggers a database backup restoration process. When that restoration executes, the stored payload runs with elevated privileges, allowing the attacker to alter database records and assume administrative control over the entire WordPress site.

Timeline

  1. September 17, 2026: The SQL injection vulnerability was officially submitted.

The Tech Race

This incident follows the pattern set by the 2024 WP-AutoPost critical vulnerability, illustrating the persistent risk posed by insecure database handling in widely used WordPress plugins. It highlights an ongoing challenge for site administrators: maintaining security across a complex, plugin-dependent software architecture.

WordPress site administrators currently using Backuply should monitor for security updates or consider disabling the plugin until a patch is confirmed. This vulnerability primarily affects site security workflows, potentially allowing unauthorized administrative access to any site running the plugin.

The takeaway

The discovery underscores the critical need for strict input validation in all data-heavy WordPress plugins. Administrators should watch for official plugin version updates to address this flaw and minimize the risk of privilege escalation.

Further reading

For broader insights on defending site infrastructure, explore Cybersecurity.

Source note: This article includes information reported by IT Security News - cybersecurity, infosecurity news.

Live Poll

Do you trust the third-party plugins you use to keep your website secure from attacks?