Everest Forms – Contact Form, Payment Form…: Improper Limitation of a Pathname to a Restricted Directory
CVE-2026-120513 is a high-severity improper limitation of a pathname to a restricted directory vulnerability in Everest Forms – Contact Form, Payment Form, Quiz, Survey & Custom Form Builder with AI from Wpeverest, with a CVSS 3.1 base score of 8.2 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected Everest Forms – Contact Form, Payment Form, Quiz, Survey & Custom Form Builder with AI versions: 3.6.2 and earlier. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.48% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of Everest Forms – Contact Form, Payment Form, Quiz, Survey & Custom Form Builder with AI you run against the affected versions below, and install the vendor's latest release.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Wpeverest | Everest Forms – Contact Form, Payment Form, Quiz, Survey & Custom Form Builder with AI | 3.6.2 and earlier | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- HighData or code can be modified at will.
- Availability
- LowPerformance or availability is reduced.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L. Scored by CNA (wordfence.com).
Official description
The Everest Forms – Contact Form, Payment Form, Quiz, Survey & Custom Form Builder with AI plugin for WordPress is vulnerable to file deletion due to insufficient file path validation in the remove_csv_file_after_email_send function in all versions up to, and including, 3.6.2 This makes it possible for unauthenticated attackers to delete files within the wp-content/uploads directory on the server, which can lead to loss of uploaded content. On hardened Apache configurations, deletion of uploads/.htaccess can re-enable PHP execution inside the uploads directory. This attack is only possible when the Save-and-Continue addon is active (EVF_SAVE_AND_CONTINUE_VERSION is defined) and the 'Disable storing entry information' setting is enabled on the target form. Escaping the uploads directory and deleting files in the site root can be possible under rare circumstances.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Limitation of a Pathname to a Restricted Directory
The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
How developers prevent this class of flaw
- For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
- Use an application firewall that can detect attacks against this weakness. It can be beneficial in cases in which the code cannot be fixed (because it is controlled by a third party), as an emergency prevention measure while more comprehensive software assurance measures are applied, or to provide defense in depth.
More Improper Limitation of a Pathname to a Restricted Directory vulnerabilities (CWE-22)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Other references
- plugins.trac.wordpress.org/browser/everest-forms/tags/3.6.2/includes/abstracts/class-evf-form-fields-upload.p…
- plugins.trac.wordpress.org/browser/everest-forms/tags/3.6.2/includes/abstracts/class-evf-form-fields-upload.p…
- plugins.trac.wordpress.org/browser/everest-forms/tags/3.6.2/includes/class-evf-ajax.php#L681
- plugins.trac.wordpress.org/browser/everest-forms/tags/3.6.2/includes/class-evf-form-task.php#L594
- plugins.trac.wordpress.org/changeset/3747723/everest-forms/trunk/includes/abstracts/class-evf-form-fields-upl…
- wordfence.com/threat-intel/vulnerabilities/id/0d61468b-8fda-4775-8099-a34ddf34566b?source=cve
Other vulnerabilities in Everest Forms – Contact Form, Payment Form, Quiz, Survey & Custom Form Builder with AI
- 7.5 High severity
Recent Improper Limitation of a Pathname to a Restricted Directory vulnerabilities
- 9.9 Critical severity
- 9.9 Critical severity
- 10.0 Critical severity
- 9.6 Critical severity
- 8.6 High severity
- 7.1 High severity
Spotted an error? Tell us.