CVE-2026-120513wpeverest Everest Forms path traversal

Schedule itHigh8.2EPSS not scored yet

CVE-2026-120513 is a path traversal in wpeverest Everest Forms, rated high (8.2 on CVSS 3.1).

Why this priority: High severity, with no exploitation signal yet.

Published 10 Nov 2026 · Updated 10 Nov 2026 · NVD status: Deferred

What it is

A file name from the request can climb out of the intended folder with sequences like ../, reaching files the service never meant to expose.

How it is reached

An attacker can exploit it over the network, without an account, and nobody has to click anything.

What an attacker gains

A successful attack can change data or behaviour. In practice, this kind of flaw lets an attacker read or write files outside the folders the service meant to expose.

Is it being exploited?

There is no public report of exploitation yet.

What to do

No fixed version is listed yet. Find every place wpeverest Everest Forms runs, watch the references for a fix, and plan a replacement if it is no longer supported.
While there is no fix, keep it off the internet or behind a VPN, allowlist or authenticating proxy.

Description from NVD

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 this means for your architecture.

A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.

Components it touches

WordPress sites and their plugins. Plugins run inside the site with its database access, and many sites are public.
File storage the service can read or write. The flaw sits between the application and the file system it can reach.

Trust boundaries in play

Internet-facing entry points. No account is needed. Any instance reachable from outside your perimeter, through a load balancer, gateway, VPN or exposed admin port, is in scope.
Between the application and the file system it can reach. An attacker who crosses it can read or write files outside the folders the service meant to expose.

Questions to answer about your own systems

Where does wpeverest Everest Forms run in your systems, and at which version?
Which of those instances can be reached from the internet or partner networks?
What can it reach once compromised: which data stores, secrets and services?

See how Veriom maps an architecture Take the interactive tour

Advisories

www.wordfence.com/threat-intel/vulnerabilities/id/0d61468b-8fda-4775-8099-a34ddf34566b?source=cve

Sources

CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.