Frontend File Manager & Sharing – User Private Files <= 1.1.1 - Missing Authorization

2022-08-06 00:00
Anonymous

Strategic Overview

Status
Patched in 1.1.2
Affected Plugin
User Private Files – WordPress File Sharing Plugin
Affected Version
<= 1.1.1
CVSS
6.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE pending
View all User Private Files – WordPress File Sharing Plugin vulnerabilities

At a glance

This record tracks a medium-severity Missing Authorization vulnerability in the User Private Files WordPress plugin, affecting versions <= 1.1.1. It carries a CVSS score of 6.3 (reachable over the network; low attack complexity). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 1.1.2; sites on affected versions should update now. Disclosed August 2022.

Vulnerability Overview

The Frontend File Manager & Sharing – User Private Files plugin for WordPress is vulnerable to authorization bypass in versions up to, and including, 1.1.1. This is due to missing capability checks and nonce validation on several functions such as dpk_upvf_rmv_file(), dpk_upvf_rmv_access(), and dpk_upvf_update_doc(). This makes it possible for unauthenticated attackers to modify several settings and modify files (via deletion and settings updates).

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-862: Missing Authorization

User Private Files <= 1.1.1 carries this weakness at dpk_upvf_rmv_file(), 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. For User Private Files the fix is 1.1.2: builds <= 1.1.1 are affected, anything from 1.1.2 onward is not.

Remediation

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

  • Login Security
  • Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/a2c5e232-3561-43a1-bdfa-4a68f20b5889

Related records

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