dbcve.org
Everest BackupWordPress extension · Everestthemes

CVE-2025-62992

HIGH · 8.1 CVSS v3.1 Published 2025-12-31
Fix available
A fix is available. Upgrade to after 2.3.9 or later.
See remediation →
88/100
Remediation priority · High
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in everestthemes Everest Backup everest-backup allows Path Traversal.This issue affects Everest Backup: from n/a through <= 2.3.11.

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.3.11 contains a Cross-Site Request Forgery (CSRF) vulnerability that can be leveraged to perform Path Traversal attacks. This allows an attacker to trick authenticated administrators into making unintended requests that access or manipulate files outside the intended backup directories.

MitigationApply the latest plugin update when available. Until then, enforce strict CSRF token validation on all state-changing backup operations and implement proper path sanitization to prevent directory traversal via user-controlled input.

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.3.9

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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. Confirm Everest Backup plugin is installed
    Navigate to WordPress admin > Plugins > Installed Plugins and look for 'Everest Backup' by Everestthemes, or inspect the plugin file at wp-content/plugins/everest-backup/everest-backup.php to read the version header comment
    Affected if The plugin is installed and the version is 2.3.9 or lower, or if the version cannot be determined (older unversioned release)
  2. Verify the plugin is active
    In WordPress admin > Plugins, check that Everest Backup shows as 'Active' under the plugin status
    Affected if The plugin is active and the backup/restore functionality is accessible in the admin dashboard
  3. Identify if backup/restore features are accessible
    Locate the Everest Backup menu item in the WordPress admin sidebar - typically found under 'Everest Backup' or 'Backups' and confirm the restore/import functionality is present
    Affected if The backup creation or restore/import features are available to administrator users without additional configuration
  4. Check for CSRF protection on backup/restore actions
    Inspect the plugin code in wp-content/plugins/everest-backup/ for nonce verification on form actions that perform backup or restore operations. Look for wp_nonce_field or check_admin_referer calls in files handling backup/restore POST requests
    Affected if The backup/restore forms lack nonce tokens or referrer validation, meaning the plugin does not implement CSRF protection on state-changing actions

You are affected if Everest Backup plugin version 2.3.9 or lower is installed and active with its backup/restore functionality accessible, and the plugin code lacks CSRF token validation on backup/restore actions.

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.

From vendor data
Upgrade available Upgrade to a release after 2.3.9
Interim mitigation

Apply the latest plugin update when available. Until then, enforce strict CSRF token validation on all state-changing backup operations and implement proper path sanitization to prevent directory traversal via user-controlled input.

Fix this in Everest Backup Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-62992 — 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-2025-62992 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