CVE-2026-39802

Everest Backup – WordPress Cloud Backup, Migration, Restore & Cloning Plugin <= 2.3.13 - Unauthenticated Remote Code Execution

2026-10-06 00:00
Muhammad Sobirov

Strategic Overview

Status
Unpatched
Affected Plugin
Everest Backup – WordPress Cloud Backup, Migration, Restore & Cloning Plugin
Affected Version
<= 2.3.13
CVSS
9.8Critical
Weakness type
CWE-94 · Improper Control of Generation of Code ('Code Injection')
CVE
CVE-2026-39802
View all Everest Backup – WordPress Cloud Backup, Migration, Restore & Cloning Plugin vulnerabilities

At a glance

CVE-2026-39802 is a critical-severity Improper Control of Generation of Code ('Code Injection') vulnerability in the Everest Backup WordPress plugin, affecting versions <= 2.3.13. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed October 2026, reported by Muhammad Sobirov.

Vulnerability Overview

The Everest Backup – WordPress Cloud Backup, Migration, Restore & Cloning Plugin plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 2.3.13. This is due to insufficient validation of user supplied input before it is executed. This makes it possible for unauthenticated attackers to execute arbitrary 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 privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-94: Improper Control of Generation of Code ('Code Injection')

Reaching this weakness in Everest Backup <= 2.3.13 takes no account at all. Code injection means input from a request reaches a language construct that evaluates code, so the attacker's text is executed rather than treated as data.

The injected code runs with the web server's privileges, giving the attacker the same access to the database and filesystem as WordPress itself. No fixed build of this plugin is recorded for Everest Backup yet, so installs running <= 2.3.13 stay exposed until the vendor ships one.

Remediation

No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.

How does WordSec protect against this?

Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: 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. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.

  • Firewall
  • Scanner
  • Login Security

External References

https://www.cve.org/CVERecord?id=CVE-2026-39802https://www.wordfence.com/threat-intel/vulnerabilities/id/a0d434ed-7ced-4a13-aa41-3be0abaebdd8https://nvd.nist.gov/vuln/detail/CVE-2026-39802

Related records

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