dbcve.org
Everest BackupWordPress extension · Everestthemes

CVE-2023-52185

HIGH · 7.5 CVSS v3.1 Published 2023-12-31
Fix available
A fix is available. Upgrade to 2.2.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Exposure of Sensitive Information to an Unauthorized Actor vulnerability in Everestthemes Everest Backup – WordPress Cloud Backup, Migration, Restore & Cloning Plugin.This issue affects Everest Backup – WordPress Cloud Backup, Migration, Restore & Cloning Plugin: from n/a through 2.1.9.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The Everest Backup WordPress plugin versions up to 2.1.9 contains an information disclosure vulnerability allowing unauthorized actors to access sensitive data. As a backup and migration plugin, this likely exposes backup files, database contents, or configuration data without proper authentication. The CVSS 7.5 score indicates high exploitability and significant impact on confidentiality.

MitigationUpdate the Everest Backup plugin to the latest version beyond 2.1.9 once available, and review server access controls to ensure backup files are not publicly accessible.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Everest BackupWordPress extension
Affected:< 2.2.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Everest Backup plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Everest Backup' by Everestthemes, or check the file /wp-content/plugins/everest-backup/ exists on the server
    Affected if The plugin is installed and active on the WordPress site
  2. Determine installed plugin version
    Open /wp-content/plugins/everest-backup/readme.txt and check the 'Stable tag' version, or inspect the main plugin PHP file for a version constant like 'version' or 'EVB_VERSION'
    Affected if The version is below 2.2.0 (versions 2.1.9 and below are vulnerable)
  3. Locate generated backup files
    Check common backup directories: /wp-content/uploads/everest-backup/, /wp-content/backup/, /wp-content/uploads/, or custom paths configured in plugin settings. Look for files with extensions .zip, .tar, .gz, .sql, .bak, .json
    Affected if Backup files exist in publicly accessible web directories
  4. Test backup file accessibility
    Attempt to download a backup file via direct URL in a browser (e.g., https://yoursite.com/wp-content/uploads/everest-backup/filename.zip). If the file downloads without authentication, it is exposed
    Affected if Backup files are directly accessible via HTTP/HTTPS without login or server-level access restrictions
  5. Check server access controls
    Review .htaccess rules in backup directories, server configuration (nginx/apache), or web.config to confirm directories deny direct file listing and download of backup extensions
    Affected if No access restrictions exist on backup directories or backup files are not protected by authentication or IP allowlisting

A site is affected if the Everest Backup plugin version is below 2.2.0 AND backup files are stored in web-accessible directories without proper authentication or access controls.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.2.0 or later
Fixed in 2.2.0
Interim mitigation

Update the Everest Backup plugin to the latest version beyond 2.1.9 once available, and review server access controls to ensure backup files are not publicly accessible.

Recommended fix High confidence

Everest Backup version 2.2.0 or later

  1. 1. Create a full backup of the WordPress site and database before updating any plugins.
  2. 2. Navigate to WordPress Admin Dashboard > Plugins.
  3. 3. Locate the Everest Backup plugin in the installed plugins list.
  4. 4. If an update is available, click 'Update Now' to upgrade to version 2.2.0 or later.
  5. 5. Alternatively, you can update via WP-CLI: wp plugin update everest-backup
  6. 6. After updating, verify the plugin version shows 2.2.0 or higher in the plugins list.
  7. 7. Test that the backup functionality works correctly after the update.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Everest Backup Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-52185 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-52185 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data