Contact Manager <= 8.6.4 - Unauthenticated Arbitrary Double File Extension Upload
Strategic Overview
- Status
- Patched in 8.6.5
- Affected Plugin
- Contact Manager
- Affected Version
<= 8.6.4- CVSS
- 8.1High
- Weakness type
- CWE-434 · Unrestricted Upload of File with Dangerous Type
- CVE
CVE-2025-1028
At a glance
CVE-2025-1028 is a high-severity Unrestricted Upload of File with Dangerous Type vulnerability in the Contact Manager WordPress plugin, affecting versions <= 8.6.4. It carries a CVSS score of 8.1 (reachable over the network; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 8.6.5; sites on affected versions should update now. Disclosed February 2025, reported by Keshav verma.
Vulnerability Overview
The Contact Manager plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the contact form upload feature in all versions up to, and including, 8.6.4. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible in specific configurations where the first extension is processed over the final. This vulnerability also requires successfully exploiting a race condition in order to exploit.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-434: Unrestricted Upload of File with Dangerous Type
Reaching this weakness in Contact Manager <= 8.6.4 takes no account at all. An unrestricted file upload lets a caller store a file whose type or destination the application does not properly constrain.
If an uploaded file lands anywhere the server will execute, the flaw becomes remote code execution and the site should be treated as fully compromised. For Contact Manager the fix is 8.6.5: builds <= 8.6.4 are affected, anything from 8.6.5 onward is not.
Remediation
Update to version 8.6.5, or a newer patched version
How does WordSec protect against this?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: Contact Manager 8.6.5 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- Login Security
External References
Related records
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C