Everest Forms <= 3.6.3 - Unauthenticated Arbitrary File Read via 'Signature' Field Meta Key Branch of attach_entry_files
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 30/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The Everest Forms plugin for WordPress is vulnerable to Arbitrary File Read in all versions up to, and including, 3.6.3 via the attach_entry_files() function. This is due to the function attaching any entry field value whose meta key matches /signature_/ to the notification email after only a file_exists() check, without validating or restricting the path. This makes it possible for unauthenticated attackers to read the contents of arbitrary files on the server, such as wp-config.php, which can contain sensitive information. Successful exploitation requires a form whose email notification has the “Attach Files” setting enabled and that contains a field with a meta key matching /signature_/ (for example, a text field labelled “Signature”), with the notification routed to an attacker-supplied email address so the exfiltrated file is delivered to the attacker. Note: The Everest Forms Pro add-on is required to exploit this vulnerability, as it provides the signature field and the email file-attachment functionality (file-email-attachments) that the attack relies on.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.5/10CVSS 7.5
- No patch5/5No patch listed yet
What would change the score
- Would score about 75 if added to CISA KEV
- Would score about 70 if CISA's SSVC rates exploitation active
- Would score about 35 if advisories confirm default setups are exposed
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-115483 (Everest Forms <= 3.6.3 - Unauthenticated Arbitrary File Read via 'Signature' Field Meta Key Branch of attach_entry_files), 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-115483 (entry last updated 2026-11-10): Affected: - wpeverest Everest Forms – Contact Form, Payment Form, Quiz, Survey & Custom Form Builder with AI: through 3.6.3 Fixed versions: none listed yet. Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. CISA KEV: CVE-2026-115483 is not listed as of cve.now's last read. This KEV status is for CVE-2026-115483 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/03f636e6-271d-4516-8db1-dc268ff794e7?source=cve - https://plugins.trac.wordpress.org/browser/everest-forms/tags/3.6.3/includes/abstracts/class-evf-form-fields-upload.php#L1727 - https://plugins.trac.wordpress.org/browser/everest-forms/tags/3.6.3/includes/abstracts/class-evf-form-fields-upload.php#L1728 - https://plugins.trac.wordpress.org/browser/everest-forms/tags/3.6.3/includes/abstracts/class-evf-form-fields-upload.php#L1735 - https://plugins.trac.wordpress.org/browser/everest-forms/tags/3.6.3/includes/abstracts/class-evf-form-fields-upload.php#L1793 - https://plugins.trac.wordpress.org/browser/everest-forms/tags/3.6.3/includes/abstracts/class-evf-form-fields-upload.php#L1816 - https://plugins.trac.wordpress.org/browser/everest-forms/tags/3.6.3/includes/abstracts/class-evf-form-fields-upload.php#L1824 - https://plugins.trac.wordpress.org/browser/everest-forms/tags/3.6.3/includes/abstracts/class-evf-form-fields-upload.php#L1637 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-115483 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-115483.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- wpeverest Everest Forms – Contact Form, Payment Form, Quiz, Survey & Custom Form Builder with AI
through 3.6.3
Evidence 17
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 15
- Link
- Link
- Link
- Link
- Link
Show all 15 sourcesShow fewer sources
- Link
- Link
- Link
- Link
- Link
- Link
- Link
- Link
- Link
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-115483
Is CVE-2026-115483 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: cve.now feed data
Which versions are affected by CVE-2026-115483?
Everest Forms – Contact Form, Payment Form, Quiz, Survey & Custom Form Builder with AI: through 3.6.3.Source: cve.now feed data