Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify exposed Wukong_HRM API
-
DeliverySend request omitting AUTH-TOKEN header
-
ExploitBypass ParamAspect authentication check
-
ExecutionInvoke HR admin API endpoints
-
ImpactExfiltrate payslips/PII and alter HR records
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Authentication mechanism validation
MITRE ATT&CK
2 techniques across 2 tactics: Defense Evasion, Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | No special conditions beyond network reachability - remote unauthenticated exploitation works against affected Wukong_HRM builds (through commit 186115e) because the ParamAspect authorization aspect treats a missing AUTH-TOKEN header as a bypass rather than a rejection, so no credentials, token, configuration change, or user interaction is required. The only real limiting factors are that the target HRM API must be network-reachable to the attacker (e.g. internet-exposed or attacker on the internal network) and the instance must be running code at or before the vulnerable commit; there is no authentication, privilege, or default-configuration barrier to overcome. |
| Impact | This is a genuine high-priority issue, not a CVSS-inflated paper risk. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H, 9.3) describes a fully remote, low-complexity, unauthenticated attack with high impact across confidentiality, integrity and availability, and the description corroborates the vector exactly: an attacker simply omits the AUTH-TOKEN header to bypass the ParamAspect authentication check and reach every HRM API endpoint. All signals align rather than conflict - the attack-vector claim (network, no privileges, no user interaction) is directly supported by the mechanism described, and three working proof-of-concept scripts (salary-slip read, employee PII export, attachment IDOR download) published by the VulnCheck-associated reporter confirm practical exploitability. Exploitation status: publicly available exploit code exists. No EPSS score was provided in the input, and this CVE is NOT listed in CISA KEV, so there is no evidence of confirmed active exploitation in the wild yet; the realistic concern is that trivial exploitation plus public POCs make opportunistic scanning likely. The main factor tempering absolute risk is deployment footprint (see prevalence), not exploit difficulty. |
| Exploit ScenarioDerived | A remote attacker discovers an internet-exposed Wukong_HRM instance and sends HRM API requests with the AUTH-TOKEN header removed, causing ParamAspect to skip authentication entirely. They then invoke administrative endpoints to read payslips and salary history, export the full employee PII dataset, and download attachments via IDOR, and can further modify or delete company-wide HR records. Public POC scripts for salary-slip read, PII export, and attachment download already automate this. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 11, 2026
Unauthenticated attackers can reach every Wukong_HRM API endpoint and operate with HR administrator privileges, because the platform's ParamAspect authorization component treats an absent AUTH-TOKEN header as an implicit pass instead of a denial. Exploitation requires nothing more than network reachability to the HRM API on a build at or before commit 186115e - no credentials, token, configuration change, or user interaction - and it exposes payslips, salary history, and employee personal data, permits attachment downloads, and allows modification or deletion of company-wide HR records. Publicly available exploit code exists (multiple proof-of-concept scripts published alongside the VulnCheck advisory), the CVSS 4.0 base score is 9.3, and no confirmed active exploitation (CISA KEV) has been reported; the risk is nevertheless genuine rather than CVSS-inflated, since the bypass is triggered by simply omitting a request header.
RemediationAI
No vendor-released patch identified at time of analysis, so remediation must currently rely on compensating controls applied at the network and gateway layers. The highest-value action is to stop unauthenticated traffic from reaching the HRM API at all: place the application behind a reverse proxy or API gateway that rejects any request to HRM endpoints lacking a valid AUTH-TOKEN header, or restrict the API entirely to an internal/VPN-only network segment - the trade-off is that this breaks legitimate clients that rely on other authentication paths, so validate the filter against known-good application flows before enforcing it. If code changes are possible, fix the root cause by making ParamAspect (com.kakarote.core.config.ParamAspect, lines 35-55 at commit 186115e1a5a0b827ad9596ff8c2f3a876fb0cc55) fail closed so a missing or empty AUTH-TOKEN header is rejected rather than permitted, and apply the same correction to the HR-specific EmployeeAspect in hrm-web; the trade-off is that a fail-closed change can break endpoints that legitimately operate without that header, so inventory them first. Because public exploit code exists - including proof-of-concept scripts for salary slip detail read, employee PII export, and attachment download IDOR published at https://github.com/AnkesKasty/cve-request-poc/blob/a7b6d1423555812d8efa26c91c5d0683164b31e5/Wukong_HRM/ (poc_salary_slip_detail_read.py, poc_employee_export_pii.py, poc_attachment_download_idor.py) - assume any exposed instance has already been probed. Therefore also review HRM access logs for requests without an AUTH-TOKEN header, audit for modified or deleted HR records and bulk exports of employee data, rotate any credentials or secrets stored in the exposed instance, and notify affected employees if data exposure is confirmed. Monitor the WuKongOpenSource repository (https://github.com/WuKongOpenSource/Wukong_HRM) and the VulnCheck advisory (https://www.vulncheck.com/advisories/wukong-hrm-through-commit-186115e-authentication-bypass-via-paramaspect) for an official fixed release and upgrade as soon as one is published.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Wukong_HRM is a Java/Spring-based open-source human resources management system (CPE cpe:2.3:a:wukongopensource:wukong_hrm). The defect sits in the shared common-web module's ParamAspect (com.kakarote.core.config.ParamAspect, lines 35-55 at commit 186115e), a Spring AOP aspect that is supposed to enforce authentication around controller invocations; instead of rejecting requests that lack the AUTH-TOKEN header, its logic allows them through, so the aspect fails open. A companion aspect, EmployeeAspect (hrm-web, com.kakarote.hrm.common.EmployeeAspect, lines 28-45), applies the same weak authorization pattern to HR-specific business logic. This maps to CWE-287 (Improper Authentication), the root-cause class covering missing or incorrect verification of a caller's identity before granting protected functionality. The assessed attack vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (original CVSS 4.0: 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, score 9.3): both vectors agree that the flaw is network-reachable, low-complexity, and requires no privileges (PR:N) and no user interaction (UI:N), while the assessment deliberately keeps the scope unchanged (S:U) and does not claim any secondary-system impact (SC/SI/SA:N). Because the vulnerable aspect sits in a shared configuration module, the missing-header bypass applies uniformly across every endpoint the application exposes, not just a single HR function - which is why the impact spans confidentiality, integrity, and availability of HR records.
Know when Wukong Hrm gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
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
Header omission gives remote unauthenticated access (AV:N/AC:L/PR:N/UI:N) to full HR admin functions, yielding high confidentiality, integrity and availability impact; scope unchanged as the app is the target.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
DescriptionCVE.org
Wukong_HRM through commit 186115e contains an authentication bypass vulnerability in ParamAspect that allows unauthenticated attackers to call every HRM API endpoint by omitting the AUTH-TOKEN header. Attackers gain HR administrator access to read payslips, salary history and employee personal data, download attachments, and modify or delete company-wide HR records.
Technical POC Analysis
Authentication bypass via fail-open authorization aspect, CWE-287.
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Latest POC
3 PoC candidates from github (unverified)
Sign in to open the public PoC links collected for this CVE.
Executive ViewAI
Wukong_HRM's API authorization bypass can expose and alter company-wide HR records, including payslips, salary history, and employee personal data, affecting the entire workforce and creating privacy, fraud, and regulatory exposure. Because affected builds at or before commit 186115e are reachable through the HRM API and publicly available exploit code exists, leadership should treat this as a critical business risk until access is restricted or a vendor fix is available. The absence of a CISA KEV listing does not reduce urgency, as no vendor-released patch has been identified at time of analysis.
No vendor-released patch identified at time of analysis. Interim mitigations: restrict Wukong_HRM API network exposure to trusted networks/VPN; enforce AUTH-TOKEN presence at the reverse proxy/WAF and deny requests lacking it; disable unused HR API endpoints; monitor and audit access to payslips, salary history, attachments, and HR record changes; rotate HR API secrets and admin credentials if compromise is suspected; isolate or shut down affected builds until a vendor fix is available.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
EUVD-2026-96701
GHSA-8w9v-279h-hchp
NVD
CVE.org
EPSS
VulDB
Exploit-DB