Skip to main content
Vulnerability Database/CVE-2026-110207

CVE-2026-110207: Wukong AICRM Auth Bypass Vulnerability

CVE-2026-110207 is an authorization bypass flaw in Wukong AICRM that allows authenticated users to access admin APIs without proper checks. Attackers can reset admin passwords and gain full control. This article covers technical details, affected versions, impact assessment, and mitigation strategies.

Published:

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-110207 Overview

CVE-2026-110207 is a missing authorization vulnerability [CWE-862] in Wukong AICRM through build 20260610. The flaw exposes user, role, department, and agent administration APIs to any authenticated user because the application performs no administrator role check. Attackers can send a POST request to /managerUser/updateUser to reset the admin account password and assign themselves the all role. The result is full administrator account takeover from a low-privileged session.

Critical Impact

Any authenticated low-privileged user can take over the Wukong AICRM administrator account by resetting its credentials and granting themselves the all role through unprotected management endpoints.

Affected Products

  • Wukong AICRM through build 20260610
  • Backend components defined in SecurityConfig.java that omit administrator role enforcement
  • Management APIs exposed via ManagerUserController and related services

Discovery Timeline

  • 2026-10-13 - CVE-2026-110207 published to NVD
  • 2026-10-14 - Last updated in NVD database

Technical Details for CVE-2026-110207

Vulnerability Analysis

Wukong AICRM exposes a set of administrative REST endpoints under paths such as /managerUser/*, /managerRole/*, and related department and agent routes. These endpoints perform operations reserved for administrators, including creating users, updating credentials, assigning roles, and modifying department structures.

The backend SecurityConfig.java registers these routes behind authentication but does not restrict them to users holding an administrator role. The controller methods in ManagerUserController and the service implementations in ManageUserServiceImpl and ManagerRoleServiceImpl also skip authorization checks before executing privileged mutations. Any authenticated session, including a newly registered or least-privileged account, can invoke these calls directly.

Root Cause

The root cause is a missing authorization check [CWE-862]. Administrative controllers rely on authentication as the sole access gate. No annotation, filter, or method-level predicate validates that the caller holds the administrator role before mutating other users, roles, or departments.

Attack Vector

The attack vector is network-based and requires only low privileges. An attacker authenticates with any valid account and submits a crafted POST request to /managerUser/updateUser targeting the administrator user ID. The request resets the administrator password and assigns the all role to the attacker-controlled account. The attacker then authenticates as the administrator or operates with full administrative privileges from their original account, achieving complete tenant takeover.

The vulnerability is described in prose because no verified proof-of-concept code is published in the referenced advisories. See the VulnCheck Advisory on Wukong-AICRM and the HackMD Missing Authorization Overview for additional technical references.

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 Attacks

Detection Methods for CVE-2026-110207

Indicators of Compromise

  • POST requests to /managerUser/updateUser, /managerUser/addUser, or /managerRole/* endpoints originating from non-administrator session tokens.
  • Unexpected password reset events on the administrator account followed by successful logins from new IP addresses.
  • Role assignment changes granting the all role to accounts that did not previously hold administrative privileges.
  • New or modified entries in the user and role database tables correlated with low-privileged session identifiers.

Detection Strategies

  • Correlate HTTP access logs with authenticated session roles and alert when administrative endpoints are invoked by non-admin users.
  • Baseline normal administrative API traffic and flag deviations in request volume or source account privilege level.
  • Inspect audit trails inside Wukong AICRM for role assignments to the all role performed by accounts other than existing administrators.

Monitoring Recommendations

  • Forward Wukong AICRM application and web server logs to a centralized analytics platform for correlation across authentication and API activity.
  • Monitor for sudden changes to the administrator account's credential hash or last-updated timestamp in the backend database.
  • Track outbound actions from accounts immediately after they invoke /managerUser/updateUser to detect follow-on abuse.

How to Mitigate CVE-2026-110207

Immediate Actions Required

  • Restrict network access to the Wukong AICRM backend so only trusted internal users can reach administrative endpoints.
  • Audit all existing user accounts and remove any unexpected members of the all role or other administrative groups.
  • Rotate the administrator password and any API credentials that may have been exposed through unauthorized role changes.
  • Review application logs for prior invocations of /managerUser/* and /managerRole/* endpoints by non-administrator accounts.

Patch Information

At the time of publication, no fixed release is listed in the NVD entry for Wukong AICRM. Review the GitHub Repository for Wukong-AICRM for updates beyond build 20260610. Operators maintaining in-house forks should add administrator role enforcement to the route definitions in SecurityConfig.java and add server-side role checks inside the Manager User Controller, Manage User Service Implementation, and Manager Role Service Implementation.

Workarounds

  • Place the application behind a reverse proxy that blocks /managerUser/*, /managerRole/*, department, and agent administration paths for all source IPs outside an administrator allowlist.
  • Disable self-registration and limit account provisioning to vetted administrators until a patched build is deployed.
  • Add a web application firewall rule that denies POST requests to /managerUser/updateUser unless the session token belongs to a known administrator account.
bash
# Example nginx reverse proxy rule restricting administrative endpoints
location ~ ^/(managerUser|managerRole)/ {
    allow 10.0.0.0/24;   # administrator subnet
    deny all;
    proxy_pass http://wukong_backend;
}

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

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.