# CVE-2026-110207: Wukong AICRM through 20260610 Missing Authorization in User and Role Management APIs

> Authenticated users can bypass authorization checks to reset admin passwords and gain full administrator privileges in Wukong AICRM.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-qhwv-w4m8-x75g

## What is CVE-2026-110207?

CVE-2026-110207 is a high-severity missing authorization vulnerability in WuKongOpenSource Wukong AICRM, published on 13 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Wukong AICRM through 20260610 contains a missing authorization vulnerability that allows any authenticated user to call user, role, department and agent administration APIs because no administrator check exists. Attackers can send POST requests to /managerUser/updateUser to reset the admin account's password and assign themselves the "all" role, achieving full administrator account takeover.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-110207 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-110207 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-110207 is a high-severity missing authorization vulnerability in WuKongOpenSource Wukong AICRM, published on 13 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-110207 exists.

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

## Sources

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

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