Quick answers
- Is CVE-2026-115483 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-115483 being exploited in the wild.
- How severe is CVE-2026-115483?
- High severity, with a CVSS score of 7.5, published 10 November 2026.
- Which products and versions are affected?
- Everest Forms up to 3.6.3.
- Is there a fix for CVE-2026-115483?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-115483 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-115483?
- Check whether you run Everest Forms at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The attach_entry_files() function in Everest Forms up to 3.6.3 attaches entry field values with meta keys matching /signature_/ to notification emails without path validation, checking only file_exists(). An unauthenticated attacker can exploit this by submitting a form with a signature field containing an arbitrary file path (e.g., /var/www/html/wp-config.php), causing the server to email the file contents to an attacker-controlled address. This requires the Pro add-on's signature field and email-attachment functionality to be active on a form routed to the attacker's email.
Affected products
- Everest Forms Everest Forms up to 3.6.3
Timeline
- 2026-11-10: disclosed