CVE-2023-4836

User Private Files < 2.0.5 - Insecure Direct Object Reference

2023-10-11 00:00
Dmitrii Ignatyev

Strategic Overview

Status
Patched in 2.0.5
Affected Plugin
User Private Files – WordPress File Sharing Plugin
Affected Version
< 2.0.5
CVSS
5.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2023-4836
View all User Private Files – WordPress File Sharing Plugin vulnerabilities

At a glance

CVE-2023-4836 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the User Private Files WordPress plugin, affecting versions < 2.0.5. 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 2.0.5; sites on affected versions should update now. Disclosed October 2023, reported by Dmitrii Ignatyev.

Vulnerability Overview

The WordPress File Sharing Plugin plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to 2.0.5 (exclusive) via the upvf_pro_preview_file function due to missing validation on a user controlled key. This makes it possible for unauthenticated attackers to gain access to files and folders belonging to other users.

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 User Private Files < 2.0.5 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. For User Private Files the fix is 2.0.5: builds < 2.0.5 are affected, anything from 2.0.5 onward is not.

Remediation

Update to version 2.0.5, 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.0.5 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2023-4836https://www.wordfence.com/threat-intel/vulnerabilities/id/e53e75be-d4d6-4c10-b192-fe9691f27dd8https://nvd.nist.gov/vuln/detail/CVE-2023-4836

Related records

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