The Rongzhitong Visual Integrated Command and Dispatch Platform is vulnerable to an unauthenticated user creation flaw, posing a significant risk of unauthorized system access.

The application fails to perform adequate authorization checks on the /dm/dispatch/user/add endpoint. This allows an unauthenticated remote attacker to successfully execute a request to create new user accounts, including sensitive initial password details.

The ability for an unauthenticated user to create accounts on a command and dispatch platform presents a severe security risk. This vulnerability can lead to unauthorized access to sensitive internal systems, data exfiltration, or the manipulation of critical dispatch operations, potentially resulting in complete system compromise or significant operational downtime. The CVSS score of 7.3 highlights the high severity of this access control failure, especially given the ease of exploitation.

Immediate Action: As no official patch is currently available, immediately restrict network access to the affected platform by placing it behind a VPN or firewall, ensuring it is not exposed to the public internet.

Proactive Monitoring: Monitor server access logs for any unauthorized GET or POST requests directed at the /dm/dispatch/user/add path and audit the user database for any suspicious or unrecognized accounts.

Compensating Controls: Deploy a Web Application Firewall (WAF) rule to explicitly block or challenge incoming traffic attempting to access the /dm/dispatch/user/add URI path from untrusted sources.

Public Exploit Available: Yes — a published proof-of-concept exists, as documented in the GitHub repository referenced in the vulnerability disclosure.

Given the lack of a vendor-provided patch and the public availability of a proof-of-concept, this vulnerability must be treated with high urgency. Organizations utilizing the Rongzhitong platform should immediately isolate the affected instance from public network segments. Ensure that strict access controls are enforced at the network perimeter until the vendor releases a secure version or a formal mitigation path is established.