CVE-2024-7848

User Private Files <= 2.1.0 - Insecure Direct Object Reference to Authenticated (Subscriber+) Private File Access

2024-08-21 00:00
Peter Thaleikis

Strategic Overview

Status
Patched in 2.1.1
Affected Plugin
User Private Files – WordPress File Sharing Plugin
Affected Version
<= 2.1.0
CVSS
4.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2024-7848
View all User Private Files – WordPress File Sharing Plugin vulnerabilities

At a glance

CVE-2024-7848 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the User Private Files WordPress plugin, affecting versions <= 2.1.0. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 2.1.1; sites on affected versions should update now. Disclosed August 2024, reported by Peter Thaleikis.

Vulnerability Overview

The User Private Files – WordPress File Sharing Plugin plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 2.1.0 via the 'dpk_upvf_update_doc' due to missing validation on the 'docid' user controlled key. This makes it possible for authenticated attackers, with subscriber-level access and above, to gain access to other user's private 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 interaction from a victim user.

CWE-639: Authorization Bypass Through User-Controlled Key

User Private Files <= 2.1.0 carries this weakness at dpk_upvf_update_doc, and reaching it takes an account at Subscriber level or above. 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 User Private Files the fix is 2.1.1: builds <= 2.1.0 are affected, anything from 2.1.1 onward is not.

Remediation

Update to version 2.1.1, or a newer patched version

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. None of that substitutes for the fix: User Private Files 2.1.1 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-7848https://www.wordfence.com/threat-intel/vulnerabilities/id/0fb06de8-97d6-46c3-83ef-93a209540259https://nvd.nist.gov/vuln/detail/CVE-2024-7848

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C