Check out the latest research from IONIX: NEW! State of the WAF Report

New CVE Detected

CVE-2026-108707 – Authentication Bypass – Wukong HRM (through commit 186115e)

Be the first to know when new zero-days emerge:

Summary

CVE-2026-108707 is a critical authentication bypass vulnerability (CWE-287, Improper Authentication) in Wukong HRM, an open-source HR management application from WuKongOpenSource. Unauthenticated attackers can call every HRM API endpoint by omitting the AUTH-TOKEN header. The CVSS v4.0 score is 9.3 (Critical).

Technical details

  • Root cause: The ParamAspect component does not enforce authentication when the AUTH-TOKEN header is missing, so requests without the header are processed as if they were authorized.
  • Trigger conditions: The attacker sends an HTTP request to an HRM API endpoint with no AUTH-TOKEN header. No credentials or user interaction are required.
  • Attack vector: Network, low complexity, no privileges required.
  • Impact: Attackers can reach HR administrator functions. These include reading payslips, salary history and employee personal data, downloading attachments, and modifying or deleting HR records. This affects the confidentiality, integrity and availability of HR data.

Affected software

  • Wukong HRM (WuKongOpenSource/Wukong_HRM) through commit 186115e1a5a0b827ad9596ff8c2f3a876fb0cc55

Severity

  • CVSS v4.0: 9.3 (Critical) – CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
  • CVSS v3.1: 9.8 (Critical) – CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: I did not find a fixed release or patched commit in the sources I reviewed. Check the upstream repository (https://github.com/WuKongOpenSource/Wukong_HRM) for a fix newer than commit 186115e and upgrade when one is available.
  • If no patch is available:
    • Do not expose Wukong HRM to the internet. Restrict access to trusted networks, for example through VPN or IP allow-lists.
    • Put a reverse proxy or WAF in front of the application that rejects API requests lacking a valid AUTH-TOKEN header.
    • Review access logs for API requests made without an AUTH-TOKEN header, and audit HR records for unauthorized access, changes or deletions.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge