On this page

Atomicorp WAF Research Note: CVE-2026-7693

Backup Migration <= 2.1.5.1 - Authenticated (Administrator+) OS Command Injection via ‘file’ Parameter

CVE Details

Status: Attack Blocked by Atomicorp
  • Already protected by existing Atomicorp WAF rules
  • Protection status: Understanding Atomicorp WAF Protection Status
  • CVE: CVE-2026-7693
  • Name: Backup Migration <= 2.1.5.1 - Authenticated (Administrator+) OS Command Injection via ‘file’ Parameter
  • Severity: High
  • CVSS: 7.2 (v3.1) (High)
  • CVSS version: 3.1
  • CVSS source: Wordfence CNA
  • CVSS vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
    • Attack vector: Network
    • Attack complexity: Low
    • Privileges required: High
    • User interaction: None
    • Scope: Unchanged
    • Confidentiality impact: High
    • Integrity impact: High
    • Availability impact: High
  • CWE: CWE-77
  • Vendor: inisev
  • Vulnerable product: Backup Migration
  • CVE published: 2026-08-05
  • CVE last modified: 2026-08-12
  • Latest Update: 2026-09-14
  • Selected Rule IDs observed: 340014 , 340023 , 344360 , 344361 , 344363 , 344364 , 344366 , 344370
  • Matching rules: 8; rules with blocking actions: 8
  • Would-block Rule IDs: 340014 , 340023 , 344360 , 344361 , 344363 , 344364 , 344366 , 344370
  • Request surfaces inspected: JSON request data, Request URI, Request argument names, Request arguments, Request cookies, SOAP request data, XML request data

Vulnerability Description

The Backup Migration plugin for WordPress is vulnerable to OS Command Injection in all versions up to, and including, 2.1.5.1 due to insufficient sanitization of the file POST parameter on the restoreBackup() AJAX handler. The handler applies esc_attr() — an HTML-context sanitizer that does not strip shell metacharacters — and concatenates the result, unquoted, into a php-cli -f … bmi_restore <file> <remote> command passed to exec(). This makes it possible for authenticated attackers, with Administrator-level access (or any user granted the plugin’s do_backups capability) and above, to execute arbitrary OS commands as the web-server user, bypassing WordPress hardening constants such as DISALLOW_FILE_EDIT and DISALLOW_FILE_MODS that would otherwise prevent code execution from the admin UI. This is an incomplete fix of CVE-2023-7002, which patched the same pattern only in the $_POST['url'] path of handleQuickMigration(); the equivalent mitigations (rawurlencode() + explicit shell-metachar replacement + double-quoting in exec()) were never applied to $backupName.

  1. Maintain the observed Atomicorp protections. Keep your Atomicorp commercial rules current and confirm that the selected observed rules (340014 , 340023 , 344360 , 344361 , 344363 , 344364 , 344366 , 344370 ) have not been locally disabled. Atomicorp commercial rules are enabled by default. If you use Atomic WAF, review the applicable policy and rule settings.

  2. Apply the vendor’s remediation. WAF protection is defense in depth and does not replace upgrading or following the affected vendor’s guidance.

    • Affected versions: inisev Backup Migration versions through 2.1.1.
    • No specific CNA/vendor solution or workaround is included in the current CVE Record . Review the vendor’s security advisories and supported-release guidance before making changes.

  3. Validate after changes. Confirm rule updates are current, review WAF events for the affected application, and test application behavior after vendor upgrades, mitigations, or local policy changes.

Research Notes

Atomicorp WAF protections are designed around attack techniques and exploit behaviors, allowing existing protections to apply across multiple vulnerabilities without requiring a unique rule for every CVE.

Public Vulnerability References

Test or Research Source

  • Source: Atomicorp AI Research Framework
  • Tags: cve, derived, rce, waf-probe

Research Note Context

This research note documents exploit-technique analysis associated with this vulnerability and references Atomicorp WAF protections observed during engineering review, testing, or validation activities.

Atomicorp security controls are generally designed to identify and mitigate attack techniques and exploit behaviors rather than individual CVE identifiers. As a result, protections developed for one vulnerability may also apply to related attack variants and future vulnerabilities using similar techniques.

Learn More

Atomicorp develops commercially supported security technologies for web applications, servers, endpoints, workloads, and legacy enterprise platforms.

Organizations interested in protecting systems against exploit techniques associated with vulnerabilities such as this one can learn more about:

  • Atomic ModSecurity Rules: commercially maintained WAF rules for ModSecurity deployments, including protections for web attacks, bots, scanners, malware, exploitation attempts, and emerging vulnerability classes.
  • Atomic WAF: an enterprise web application firewall with Atomicorp rules, centralized management, reporting, authentication controls, and operational tooling.
  • Atomic ModSecurity Integrator: a special licensing option for MSPs, MSSPs, OEMs, VARs, reverse proxy providers, and other integrators who want to incorporate Atomicorp ModSecurity rule technology into their own products or services.
  • Atomic OSSEC: an enterprise OSSEC-based intrusion detection, compliance, and security monitoring platform.
  • Atomic Protector: workload protection for Linux, web, cloud, data center, and hybrid environments.

For additional information, product evaluations, or technical discussions, visit https://www.atomicorp.com/ or https://modsecurity.io/ .