Skip to main content
VulnerabilityPublished Updated

CVE-2026-97332: User Private Files (WordPress plugin) · Improper Access Control

Affects User Private Files (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.3 Medium : upgrade to 2.2.0 when convenient.

Data as of 15 Nov 2026, 20:25 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.2.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    Public exploit code: GitHub proofs of concept

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Upgrade User Private Files (WordPress plugin) to 2.2.0.

Affected software

ProductAffectedFixed in
User Private FilesAffected
  • <2.2.0
Fixed in
  • 2.2.0

AI-suggested

A fixed version 2.2.0 of the User Private Files plugin addresses this issue. Users should upgrade to version 2.2.0 or later to remediate the vulnerability. No vendor advisory or patch link was provided, so verify the fix availability from the plugin's official source before upgrading. Until patched, restrict access to the affected plugin or disable it on multisite installations if possible.

Description

A vulnerability in the User Private Files WordPress plugin before version 2.2.0 allows unauthenticated users on multisite installations to access other users' private files. This occurs because the rewrite rule that enforces access control is bypassed, exposing private files directly. The issue is classified as improper access control (CWE-284).

References

Community reviews

Loading reviews…