# CVE-2026-112785: OpenCATS before 0.10.0 Missing Authorization in Saved-List AJAX Endpoints


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** GHSA-q7v9-9q5g-w293

## What is CVE-2026-112785?

CVE-2026-112785 is a medium-severity vulnerability in OpenCATS, published on 20 Oct 2026. 

### Official description

OpenCATS before 0.10.0 contains a missing authorization vulnerability that allows READ-level users to create, rename, delete, and populate saved lists via AJAX endpoints. Authenticated attackers can send requests to newList.php, editListName.php, deleteList.php, or addToLists.php with any savedListID to alter or delete any saved list site-wide.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-112785 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-112785 is a medium-severity vulnerability in OpenCATS, published on 20 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-112785 in the wild and no public exploit code.

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

## Sources

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

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