Strategic Overview
- Status
- Unpatched
- Affected Plugin
- WSM Downloader
- Affected Version
<= 1.4.0- CVSS
- 5.3Medium
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2022-2367
At a glance
CVE-2022-2367 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the WSM Downloader WordPress plugin, affecting versions <= 1.4.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 July 2022, reported by Raad Haddad.
Vulnerability Overview
The WSM Downloader for WordPress is vulnerable to domain bypass due to insufficient hostname validation in the wsmd_user_download_request AJAX action in versions up to, and including, 1.4.0. This makes it possible for unauthenticated attackers to bypass domain name restrictions on download links to download files from non-acceptable files.
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-639: Authorization Bypass Through User-Controlled Key
Reaching this weakness in WSM Downloader <= 1.4.0 takes a caller who can reach the endpoint. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.
Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. No fixed build of this plugin is recorded for WSM Downloader yet, so installs running <= 1.4.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 WSM Downloader
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C