CVE-2025-2257

Total Upkeep – WordPress Backup Plugin plus Restore & Migrate by BoldGrid <= 1.16.10 - Authenticated (Admin+) Command Injection

2025-03-25 00:00
sterva

Strategic Overview

Status
Patched in 1.17.0
Affected Version
<= 1.16.10
CVSS
7.2High
Weakness type
CWE-78 · Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
CVE
CVE-2025-2257
View all Total Upkeep – WordPress Backup Plugin plus Restore & Migrate by BoldGrid vulnerabilities

At a glance

CVE-2025-2257 is a high-severity Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') vulnerability in the Total Upkeep WordPress plugin, affecting versions <= 1.16.10. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Admin level or above. The issue is fixed in version 1.17.0; sites on affected versions should update now. Disclosed March 2025, reported by sterva.

Vulnerability Overview

The Total Upkeep – WordPress Backup Plugin plus Restore & Migrate by BoldGrid plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1.16.10 via the compression_level setting. This is due to the plugin using the compression_level setting in proc_open() without any validation. This makes it possible for authenticated attackers, with administrator-level access and above, to execute code on the server.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')

The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component.

Remediation

Update to version 1.17.0, or a newer patched version

How does WordSec protect against this?

An attacker needs Admin access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: Total Upkeep 1.17.0 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C