# CVE-2026-119657: FilePress through 3.0.1 Missing Authorization in PicHome Library Folder Operations


- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 30 Oct 2026
- **Updated:** 30 Oct 2026
- **Also known as:** GHSA-6vrq-vfh4-v7v2

## What is CVE-2026-119657?

CVE-2026-119657 is a low-severity vulnerability in zyx0814 FilePress, published on 30 Oct 2026. 

### Official description

FilePress through 3.0.1 contains a missing authorization vulnerability in dzz/pichome/library that allows authenticated users to manage other libraries' folders because checkuserperm_by_uid only checks membership of any library. Attackers who know another library's appid or folder id can invoke folder.php operations like deletefolder and rename, or rightdata.php getfolderdata, to delete, modify, or read foreign folders.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-119657 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-119657 is a low-severity vulnerability in zyx0814 FilePress, published on 30 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-119657 in the wild and no public exploit code.

Affected product: zyx0814 FilePress. 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-119657/ (Markdown: https://insights.sbomify.com/CVE-2026-119657/index.md)
```

## Sources

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

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