CVE-2026-5478: Everest Forms <= 3.4.4 - Unauthenticated Arbitrary File Read and Deletion via Upload Field 'old_files' Parameter
The Everest Forms plugin for WordPress is vulnerable to Arbitrary File Read and Deletion in all versions up to, and including, 3.4.4. This is due to the plugin trusting attacker-controlled oldfiles data from public form submissions as legitimate server-side upload state, and converting attacker-supplied URLs into local filesystem paths using regex-based string replacement without canonicalization or directory boundary enforcement. This makes it possible for unauthenticated attackers to read arbitrary local files (e.g., wp-config.php) by injecting path-traversal payloads into the oldfiles upload field parameter, which are then attached to notification emails. The same path resolution is also used in the post-email cleanup routine, which calls unlink() on the resolved path, resulting in the targeted file being deleted after being attached. This can lead to full site compromise through disclosure of database credentials and authentication salts from wp-config.php, and denial of service through deletion of critical files. Prerequisite: The form must contain a file-upload or image-upload field, and disable storing entry information.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-5478?
CVE-2026-5478 is considered a high severity vulnerability due to the potential for unauthorized file access and deletion.
How do I fix CVE-2026-5478?
To fix CVE-2026-5478, update the Everest Forms plugin to version 3.4.5 or higher, where the vulnerability has been addressed.
What type of attack does CVE-2026-5478 enable?
CVE-2026-5478 enables attackers to perform unauthenticated arbitrary file read and deletion attacks through the plugin's upload field.
Which versions of Everest Forms are affected by CVE-2026-5478?
All versions of Everest Forms up to and including 3.4.4 are affected by CVE-2026-5478.
Is user authentication required to exploit CVE-2026-5478?
No, CVE-2026-5478 can be exploited without any user authentication, making it particularly dangerous.