# CVE-2026-108708: Wukong_HRM through commit 186115e Missing Authorization via EmployeeAspect and EmployeeUtil

> Low-privileged employees can access and modify sensitive HR data company-wide due to missing authorization checks in Wukong_HRM.

- **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:** 11 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-j95x-qfc5-mfv5

## What is CVE-2026-108708?

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

### Official description

Wukong_HRM through commit 186115e contains a missing authorization vulnerability because EmployeeAspect assigns every caller the HR administrator role and EmployeeUtil data-scope checks return all employees. Any authenticated low-privileged employee can read payslips, salary records, bank cards and personal data, edit bank cards, and delete employees, departments and contracts company-wide.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-108708 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-108708 is a high-severity missing authorization vulnerability in WuKongOpenSource Wukong_HRM, published on 11 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-108708 exists.

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

## Sources

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

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