dbcve.org
Everest FormsWordPress extension · Wpeverest

CVE-2025-5927

HIGH · 7.5 CVSS v3.1 Published 2025-06-25
Fix available
A fix is available. Upgrade to 1.9.5 or later.
See remediation →
82/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
The Everest Forms (Pro) plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the delete_entry_files() function in all versions up to, and including, 1.9.4. This makes it possible for unauthenticated attackers to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php). The vulnerability requires an admin to trigger the deletion via deletion of a form entry and cannot be carried out by the attacker alone.

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 Forms Pro plugin for WordPress is vulnerable to arbitrary file deletion via the delete_entry_files() function due to insufficient path validation. Unauthenticated attackers can trick an administrator into deleting form entries, causing the plugin to delete arbitrary server files including critical files like wp-config.php, leading to potential remote code execution.

MitigationUpdate to Everest Forms Pro version 1.9.5 or later which contains the path validation fix. Also ensure proper file permissions are in place and maintain backups to limit damage if exploitation occurs.

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 FormsWordPress extension
Affected:< 1.9.5

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

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

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 Forms plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Everest Forms' or 'Everest Forms Pro'. Alternatively, check the /wp-content/plugins/everest-forms/ directory exists.
    Affected if Everest Forms or Everest Forms Pro plugin is present on the WordPress site
  2. Determine installed plugin version
    In WordPress admin Plugins list, click on the Everest Forms plugin to view version details. Or check the main plugin file header in /wp-content/plugins/everest-forms/everest-forms.php for the 'Version' comment.
    Affected if Version is less than 1.9.5 (e.g., 1.9.4, 1.9.3, etc.)
  3. Confirm delete_entry_files function is accessible
    Check if the plugin handles form entry deletion. This function processes file attachments when form entries are deleted. The vulnerability allows path traversal via entry deletion requests.
    Affected if The plugin handles form entry file attachments and the delete_entry_files function processes deletion requests without proper path validation

The site is affected if Everest Forms (Pro) plugin version is below 1.9.5 and handles form entry deletions, allowing unauthenticated path traversal to delete arbitrary files.

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 1.9.5 or later
Fixed in 1.9.5
Interim mitigation

Update to Everest Forms Pro version 1.9.5 or later which contains the path validation fix. Also ensure proper file permissions are in place and maintain backups to limit damage if exploitation occurs.

Recommended fix High confidence

Everest Forms 1.9.5

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate Everest Forms (or Everest Forms Pro) in the plugin list
  4. If an update is available, click 'Update Now' to update to version 1.9.5
  5. Alternatively, go to Dashboard > Updates and update all plugins including Everest Forms
  6. Verify the updated version by checking the plugin version number in the plugins list

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

Fix this in Everest Forms Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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