dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-10304

MEDIUM · 5.3 CVSS v3.1 Published 2025-12-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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
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 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 · high confidence

The Everest Backup WordPress plugin has an authorization bypass vulnerability in the process_status_unlink() function. This function lacks both a capability check (current_user_can) and nonce verification, allowing unauthenticated attackers to delete backup progress files via direct function calls. This causes in-progress backups to fail, effectively creating a denial-of-service condition against the backup system.

MitigationUpdate the plugin to the latest version (after 2.3.8) which should include proper capability checks and nonce verification on the process_status_unlink() function. If no update is available, implement manual hardening by adding current_user_can('manage_options') checks and wp_verify_nonce validation before file deletion operations.

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

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
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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. Locate the Everest Backup plugin version
    In WordPress admin, go to Plugins > Installed Plugins > find Everest Backup and read the version number displayed beneath the plugin name
    Affected if The installed version is prior to 2.3.8
  2. Confirm the plugin is active
    Check the WordPress plugins list to verify Everest Backup has the 'Active' status indicator
    Affected if The plugin is active and the version is unpatched
  3. Inspect the plugin file containing process_status_unlink()
    Navigate to the plugin directory (wp-content/plugins/everest-backup/) and locate the file containing the process_status_unlink() function, typically in includes/ or classes/ folders
    Affected if The function exists in the plugin code and lacks current_user_can() and wp_verify_nonce() calls before file operations
  4. Verify the vulnerable function is accessible
    Search the plugin files for the process_status_unlink function definition and check if it has any capability checks or nonce validation at the beginning of the function
    Affected if No capability check (current_user_can) and no nonce verification (wp_verify_nonce) are present in the function
  5. Confirm the AJAX or action hook registration
    Examine how process_status_unlink is registered (via add_action or add_ajax) and check if it is hooked to a public-facing WordPress action without authentication requirements
    Affected if The function is hooked to an AJAX endpoint or action that can be called by unauthenticated users

The environment is affected if the Everest Backup plugin version is unpatched (prior to 2.3.8), the plugin is active, and the process_status_unlink function lacks both capability checks and nonce verification, allowing unauthenticated access.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to the latest version (after 2.3.8) which should include proper capability checks and nonce verification on the process_status_unlink() function. If no update is available, implement manual hardening by adding current_user_can('manage_options') checks and wp_verify_nonce validation before file deletion operations.

Recommended fix Moderate confidence

Version 2.3.9 or later

  1. Check your current Everest Backup plugin version in WordPress admin under Plugins > Installed Plugins
  2. Navigate to Dashboard > Updates or Plugins > Add New > Upload Plugin
  3. Update to version 2.3.9 or later which contains the security fix for the missing authorization vulnerability
  4. Verify the update completed successfully and the plugin is active
  5. Monitor backup operations to confirm they complete without unauthorized interruption

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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