Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-108707 Overview
CVE-2026-108707 is an authentication bypass vulnerability in Wukong_HRM, an open-source human resource management platform. The flaw resides in the ParamAspect class and affects the project through commit 186115e. An unauthenticated remote attacker can invoke any HRM API endpoint by omitting the AUTH-TOKEN header. Successful exploitation grants HR administrator-level access, exposing payslips, salary history, employee personal data, and file attachments. Attackers can also modify or delete company-wide HR records. The vulnerability is tracked under CWE-287: Improper Authentication.
Critical Impact
Unauthenticated attackers can read, modify, and delete all HR records including salary data, payslips, and personally identifiable information (PII).
Affected Products
- Wukong_HRM through commit 186115e
- common-web module containing ParamAspect.java
- hrm-web module containing EmployeeAspect.java
Discovery Timeline
- 2026-10-11 - CVE-2026-108707 published to NVD
- 2026-10-16 - Last updated in NVD database
Technical Details for CVE-2026-108707
Vulnerability Analysis
The root defect lies in how ParamAspect enforces authentication across HRM API endpoints. The aspect inspects the inbound AUTH-TOKEN header to resolve the calling user context before controller logic executes. When the header is absent, the aspect fails open rather than rejecting the request. Downstream code then treats the request as privileged and executes HR administrator operations. This allows unauthenticated callers to reach every protected endpoint, including those serving salary slips, employee exports, and attachment downloads. Public proof-of-concept scripts demonstrate direct extraction of PII, payroll data, and file attachments from vulnerable deployments.
Root Cause
The ParamAspect interceptor contains logic that only applies authentication checks when the AUTH-TOKEN header is present and non-empty. By omitting the header entirely, the request skips the token validation branch. The companion EmployeeAspect likewise relies on the presence of authenticated user context and does not enforce a deny-by-default policy. The combination produces a classic failure of implicit trust in client-supplied headers.
Attack Vector
Exploitation requires only network reachability to the Wukong_HRM API. An attacker issues standard HTTP requests to any HRM endpoint without supplying the AUTH-TOKEN header. The server processes the request as an authorized HR administrator operation. Public PoCs on GitHub demonstrate three attack paths: insecure direct object reference (IDOR) on attachment downloads, bulk employee PII export, and detailed salary slip retrieval. No credentials, user interaction, or privileged position in the network are required.
Refer to the published analysis for mechanism details: VulnCheck Advisory: Authentication Bypass and the ParamAspect source.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-108707
Indicators of Compromise
- HTTP requests to /hrm/* or other Wukong_HRM API paths that lack an AUTH-TOKEN request header.
- Bulk calls to employee export, salary slip detail, or attachment download endpoints from a single source IP.
- Unexpected outbound transfers of HR data or large response bodies from the HRM application server.
- Access patterns matching the public PoC scripts referenced in the GitHub PoC: PII Export and GitHub PoC: Salary Slip.
Detection Strategies
- Deploy a web application firewall (WAF) rule that blocks any request to HRM API paths missing the AUTH-TOKEN header.
- Enable application-level logging of request headers and alert on authenticated endpoints receiving tokenless requests.
- Correlate HR API access volume by source IP to surface automated scraping behavior.
Monitoring Recommendations
- Forward Wukong_HRM access logs and reverse proxy logs to a centralized logging platform for retention and query.
- Build alerts for anomalous read volumes against payroll, employee, and attachment endpoints.
- Monitor for new external IP ranges contacting the HRM application outside normal business geographies.
How to Mitigate CVE-2026-108707
Immediate Actions Required
- Restrict network access to the Wukong_HRM application to trusted corporate networks or VPN users only.
- Place the application behind a reverse proxy or WAF that rejects any API request missing the AUTH-TOKEN header.
- Audit access logs since deployment for tokenless requests and investigate any confirmed data exposure.
- Rotate credentials and notify affected employees if PII or payroll data exposure is confirmed.
Patch Information
No official vendor patch is referenced in the advisory at the time of publication. Operators should monitor the Wukong_HRM repository for a fix that updates ParamAspect and EmployeeAspect to enforce deny-by-default when the AUTH-TOKEN header is absent or invalid. Review the VulnCheck Advisory for ongoing status.
Workarounds
- Add an upstream filter (nginx, Apache, or API gateway) that returns 401 Unauthorized for any HRM API request lacking a non-empty AUTH-TOKEN header.
- Enforce mutual TLS or IP allowlisting on the HRM API to prevent anonymous external access.
- Remove public internet exposure of the HRM application until a validated code fix is applied.
- Apply a local code change to ParamAspect.java that rejects requests when AUTH-TOKEN resolution fails, rather than continuing execution.
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

