Everest Backup <= 2.1.9 - Sensitive Information Exposure via Log File
Strategic Overview
- Status
- Patched in 2.2.0
- Affected Version
< 2.2.0- CVSS
- 7.5High
- Weakness type
- CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
- CVE
CVE-2023-52185
At a glance
CVE-2023-52185 is a high-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Everest Backup WordPress plugin, affecting versions < 2.2.0. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires no authentication. The issue is fixed in version 2.2.0; sites on affected versions should update now. Disclosed December 2023, reported by Joshua Chan.
Vulnerability Overview
The Everest Backup – WordPress Cloud Backup, Migration, Restore & Cloning Plugin plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to 2.2.0 (exclusive) via the plugin's log file. This makes it possible for unauthenticated attackers to extract sensitive data including the locations of backups.
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.
CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Reaching this weakness in Everest Backup < 2.2.0 takes a caller who can reach the endpoint. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.
The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For Everest Backup the fix is 2.2.0: builds < 2.2.0 are affected, anything from 2.2.0 onward is not.
Remediation
Update to version 2.2.0, or a newer patched version
How does WordSec protect against this?
The fix is the thing that ends this: Everest Backup 2.2.0 closes this, and updating the plugin is the step that ends it.
- Alerts
External References
Related records
Other vulnerabilities in Everest Backup – WordPress Cloud Backup, Migration, Restore & Cloning Plugin
- 7.5CVE-2026-66472: Everest Backup SQL Injection
CVE-2026-66472 - 7.5CVE-2024-10028: Everest Backup Sensitive Invormation Disclosure
CVE-2024-10028 - 7.2CVE-2023-7201: Everest Backup <= 2.2.4 Arbitrary File Upload
CVE-2023-7201 - 5.9CVE-2025-11380: Everest Backup Unauthenticated Information Exposure
CVE-2025-11380 - 5.3CVE-2025-10304: Everest Backup Unauthenticated Backup Failure
CVE-2025-10304 - 5.3CVE-2025-62946: Everest Backup <= 2.3.8 Missing Authorization
CVE-2025-62946 - 4.3CVE-2025-62992: Everest Backup <= 2.3.9 Cross-Site Request Forgery
CVE-2025-62992 - 4.3CVE-2025-49238: Everest Backup <= 2.3.3 Cross-Site Request Forgery
CVE-2025-49238
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C