Website support, maintenance and fixes for UK businessesCall 0208 088 8371info@websupportservices.co.uk

HomeWordPress vulnerabilitiesUser Private Files

User Private Files vulnerabilities

User Private Files has 7 known vulnerabilities in this database. The most recent published record is dated 7 Oct 2026.

Known vulnerabilities
7
Active installs
1,000+
Latest version
2.2.0
Last updated
1 Oct 2026
Most recent
7 Oct 2026

Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.

VulnerabilitySeverityAffectedFixPublished
Sensitive data exposure
CVE-2026-97331
Medium 4.3Before 2.1.9Fixed in 2.1.918 h ago
Broken access control
CVE-2026-97332
Medium 5.3Before 2.2.0Fixed in 2.2.03 d ago
Cross-site scripting (XSS)
CVE-2026-10093
Medium 6.4Up to 2.1.6Fixed in a later version (latest 2.2.0)16 Jun 2026
Cross-site scripting (XSS)
CVE-2024-13799
Medium 6.4Up to 2.1.3Fixed in a later version (latest 2.2.0)19 Feb 2025
Broken access control
CVE-2024-7848
Medium 4.3Before 2.1.1Fixed in 2.1.122 Aug 2024
Cross-site scripting (XSS)
CVE-2023-4636
Medium 4.4Up to 2.0.3Fixed in a later version (latest 2.2.0)5 Sep 2023
Arbitrary file upload
CVE-2022-2356
High 8.8Before 1.1.3Fixed in 1.1.38 Aug 2022
Read the published descriptions
CVE-2026-97331, 7 Oct 2026
The User Private Files WordPress plugin before 2.1.9 does not validate that a supplied user belongs to the document being operated on before returning that user's email address, allowing any authenticated user, such as a Subscriber, to obtain the email address of any registered account, including administrators. CVE record
CVE-2026-97332, 4 Oct 2026
The User Private Files WordPress plugin before 2.2.0 does not properly protect its stored private files on multisite installations, where the rewrite rule it relies on to route file requests through its access check is never reached, allowing unauthenticated users to retrieve other users' private files directly. CVE record
CVE-2026-10093, 16 Jun 2026
The File Sharing & Download Manager - User Private Files plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'fldr_ttl' parameter in all versions up to, and including, 2.1.6 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
CVE-2024-13799, 19 Feb 2025
The User Private Files - File Upload & Download Manager with Secure File Sharing plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘new-fldr-name’ parameter in all versions up to, and including, 2.1.3 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
CVE-2024-7848, 22 Aug 2024
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. CVE record
CVE-2023-4636, 5 Sep 2023
The WordPress File Sharing Plugin plugin for WordPress is vulnerable to Stored Cross-Site Scripting via admin settings in versions up to, and including, 2.0.3 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-level permissions and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This only affects multi-site installations and installations where unfiltered_html has been disabled. CVE record
CVE-2022-2356, 8 Aug 2022
The Frontend File Manager & Sharing WordPress plugin before 1.1.3 does not filter file extensions when letting users upload files on the server, which may lead to malicious code being uploaded. CVE record

What to do if you run User Private Files

If you run User Private Files, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.

If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.

Email me about new User Private Files vulnerabilities

Free. We email you when a new vulnerability is published for User Private Files, usually within minutes. Confirm by email; unsubscribe any time.

Focus on your business. We’ll take care of your website.

From everyday updates to ongoing care, we keep your website working.

Get website support