# CVE-2026-123782: ChatWiki before 2.10.0 Cross-Tenant IDOR via SaveFormField and UpdateFormRequired


- **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:** 6 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-7pjf-qfpr-qf9x

## What is CVE-2026-123782?

CVE-2026-123782 is a medium-severity vulnerability in zhimaAi chatwiki, published on 6 Nov 2026. 

### Official description

ChatWiki before 2.10.0 contains an insecure direct object reference vulnerability in SaveFormField and UpdateFormRequired that allows authenticated users to modify other tenants' form fields. Attackers can pass their own form_id to satisfy the ownership check alongside another tenant's sequential form_field id to alter field names, descriptions, types and required flags, disrupting how submitted entries are stored.

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

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


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

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

## Is CVE-2026-123782 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-123782 is a medium-severity vulnerability in zhimaAi chatwiki, published on 6 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-123782 in the wild and no public exploit code.

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

## Sources

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

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