Frontend File Manager & Sharing – User Private Files <= 1.1.0 - Sensitive Information Disclosure

2022-08-06 00:00
Anonymous

Strategic Overview

Status
Patched in 1.1.1
Affected Plugin
User Private Files – WordPress File Sharing Plugin
Affected Version
<= 1.1.0
CVSS
5.3Medium
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE pending
View all User Private Files – WordPress File Sharing Plugin vulnerabilities

At a glance

This record tracks a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the User Private Files WordPress plugin, affecting versions <= 1.1.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 1.1.1; 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 Sensitive Data Exposure in versions up to, and including, 1.1.0 via the dpk_upvf_uemail_search() function. This can allow unauthenticated attackers to extract sensitive data including user emails.

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-200: Exposure of Sensitive Information to an Unauthorized Actor

User Private Files <= 1.1.0 carries this weakness at dpk_upvf_uemail_search(), and reaching it takes a caller who can reach the endpoint. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For User Private Files the fix is 1.1.1: builds <= 1.1.0 are affected, anything from 1.1.1 onward is not.

Remediation

Update to version 1.1.1, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: User Private Files 1.1.1 closes this, and updating the plugin is the step that ends it.

  • Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/afc9114b-80b7-4caf-ab6b-35747ff5057b

Related records

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