# CVE-2026-97332: User Private Files < 2.2.0 - Unauthenticated Private File Disclosure via .htaccess Rewrite Rule Bypass (Multisite)

> Unauthenticated attackers can access other users' private files on multisite installations due to a bypassed access control mechanism.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Oct 2026
- **Updated:** 9 Oct 2026
- **Also known as:** GHSA-rgr9-g879-r5wm

## What is CVE-2026-97332?

CVE-2026-97332 is a medium-severity missing authorization vulnerability in Unknown User Private Files, published on 4 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-97332?


## How do I fix CVE-2026-97332?

No fix has been published for CVE-2026-97332 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-97332 being exploited?

There is no known exploitation of CVE-2026-97332 in the wild and no public exploit code.

Public exploit code:

- Independent PoC and reproducible lab for CVE-2026-97332 — User Private Files < 2.2.0 unauthenticated private file disclosure on WordPress Multisite. (github_poc): https://github.com/Kolya080808/CVE-2026-97332-PoC

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-97332 and fix it if it is affected.

What it is: CVE-2026-97332 is a medium-severity missing authorization vulnerability in Unknown User Private Files, published on 4 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-97332 in the wild and no public exploit code.

Affected product: Unknown User Private Files. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-97332/ (Markdown: https://insights.sbomify.com/CVE-2026-97332/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-97332
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-97332
- OSV: https://osv.dev/vulnerability/CVE-2026-97332

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-97332/
Summaries are generated and may contain mistakes; the official description above is the record.