PeepSo Core: File Uploads <= 6.4.6.0 - Insecure Direct Object Reference to Unauthenticated Sensitive Information Exposure via file_download
Strategic Overview
- Status
- Patched in 6.4.6.1
- Affected Plugin
- PeepSo Core: File Uploads
- Affected Version
<= 6.4.6.0- CVSS
- 5.3Medium
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2024-8988
At a glance
CVE-2024-8988 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the PeepSo Core WordPress plugin, affecting versions <= 6.4.6.0. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 6.4.6.1; sites on affected versions should update now. Disclosed May 2025, reported by Bikram Kharal (themarkib).
Vulnerability Overview
The PeepSo Core: File Uploads plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 6.4.6.0 via the file_download REST API endpoint due to missing validation on a user controlled key. This makes it possible for unauthenticated attackers to download files uploaded by others users and expose potentially sensitive information.
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 PeepSo Core <= 6.4.6.0 takes no account at all. 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. For PeepSo Core the fix is 6.4.6.1: builds <= 6.4.6.0 are affected, anything from 6.4.6.1 onward is not.
Remediation
Update to version 6.4.6.1, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: PeepSo Core 6.4.6.1 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C