WCP Contact Form <= 3.1.0 - Missing Authorization via downloadCsv
Strategic Overview
- Status
- Unpatched
- Affected Plugin
- WCP Contact Form
- Affected Version
<= 3.1.0- CVSS
- 5.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2023-32520
At a glance
CVE-2023-32520 is a medium-severity Missing Authorization vulnerability in the WCP Contact Form WordPress plugin, affecting versions <= 3.1.0. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed May 2023, reported by thiennv.
Vulnerability Overview
The WCP Contact Form plugin for WordPress is vulnerable to unauthorized disclosure of data due to a missing capability check on the downloadCsv() function hooked via plugins_loaded in versions up to, and including, 3.1.0. This makes it possible for unauthenticated attackers to export submitted form data.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-862: Missing Authorization
WCP Contact Form <= 3.1.0 carries this weakness at downloadCsv(), and reaching it takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. No fixed build of this plugin is recorded for WCP Contact Form yet, so installs running <= 3.1.0 stay exposed until the vendor ships one.
Remediation
No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in WCP Contact Form
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C