CVE-2025-11380

Everest Backup <= 2.3.5 - Missing Authorization to Unauthenticated Information Exposure

2025-10-10 00:00
netranger

Strategic Overview

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

At a glance

CVE-2025-11380 is a medium-severity Missing Authorization vulnerability in the Everest Backup WordPress plugin, affecting versions <= 2.3.5. It carries a CVSS score of 5.9 (reachable over the network; high confidentiality impact). Exploitation requires no authentication. The issue is fixed in version 2.3.6; sites on affected versions should update now. Disclosed October 2025, reported by netranger.

Vulnerability Overview

The Everest Backup – WordPress Cloud Backup, Migration, Restore & Cloning Plugin plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the 'everest_process_status' AJAX action in all versions up to, and including, 2.3.5. This makes it possible for unauthenticated attackers to retrieve back-up file locations that can be subsequently accessed and downloaded. This does require a back-up to be running in order for an attacker to retrieve the back-up location.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality.

CWE-862: Missing Authorization

Everest Backup <= 2.3.5 carries this weakness at everest_process_status, 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.6: builds <= 2.3.5 are affected, anything from 2.3.6 onward is not.

Remediation

Update to version 2.3.6, 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.6 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-11380https://www.wordfence.com/threat-intel/vulnerabilities/id/869d7cab-cf21-4168-b45d-1681c76d896chttps://nvd.nist.gov/vuln/detail/CVE-2025-11380

Related records

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