CVE-2025-10304

Everest Backup – WordPress Cloud Backup, Migration, Restore & Cloning Plugin <= 2.3.8 - Missing Authorization to Unauthenticated Backup Failure

2025-12-02 15:27
Jonas Benjamin Friedli

Strategic Overview

Status
Patched in 2.3.9
Affected Plugin
Everest Backup – WordPress Cloud Backup, Migration, Restore & Cloning Plugin
Affected Version
<= 2.3.8
CVSS
5.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2025-10304
View all Everest Backup – WordPress Cloud Backup, Migration, Restore & Cloning Plugin vulnerabilities

At a glance

CVE-2025-10304 is a medium-severity Missing Authorization vulnerability in the Everest Backup WordPress plugin, affecting versions <= 2.3.8. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.3.9; sites on affected versions should update now. Disclosed December 2025, reported by Jonas Benjamin Friedli.

Vulnerability Overview

The Everest Backup – WordPress Cloud Backup, Migration, Restore & Cloning Plugin plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on the process_status_unlink() function in all versions up to, and including, 2.3.8. This makes it possible for unauthenticated attackers to delete the back-up progress files and cause a back-up to fail while it is in progress.

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.

CWE-862: Missing Authorization

Everest Backup <= 2.3.8 carries this weakness at process_status_unlink(), and reaching it takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Everest Backup the fix is 2.3.9: builds <= 2.3.8 are affected, anything from 2.3.9 onward is not.

Remediation

Update to version 2.3.9, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Everest Backup 2.3.9 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-10304https://www.wordfence.com/threat-intel/vulnerabilities/id/f7d7c619-7dc0-47a5-a203-6df4dfa0158bhttps://nvd.nist.gov/vuln/detail/CVE-2025-10304

Related records

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