CVE-2024-8669
Published: 14 September 2024
Summary
CVE-2024-8669 is a critical-severity SQL Injection (CWE-89) vulnerability in Softaculous Backuply. Its CVSS base score is 9.1 (Critical).
Operationally, ranked in the top 10.0% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis
The Backuply – Backup, Restore, Migrate and Clone plugin for WordPress is vulnerable to SQL injection in the backuply_wp_clone_sql() function. The flaw stems from insufficient escaping of the user-supplied 'options' parameter and the absence of prepared statements, allowing an attacker to append arbitrary SQL to existing queries. All versions through 1.3.4 are affected.
An authenticated user with administrator privileges can exploit the issue over the network to extract sensitive data from the database. The CVSS 9.1 score reflects high confidentiality, integrity, and availability impact when the attack succeeds.
Public references point to the vulnerable code in the plugin repository and a subsequent changeset that addresses the parameter handling. Administrators should apply the available update that resolves the injection vector in versions after 1.3.4. The associated EPSS score has remained flat at 0.0502 with no material increase since disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-49339
Vulnerability details
The Backuply – Backup, Restore, Migrate and Clone plugin for WordPress is vulnerable to SQL Injection via the 'options' parameter passed to the backuply_wp_clone_sql() function in all versions up to, and including, 1.3.4 due to insufficient escaping on the user…
more
supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with administrator-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.