CVE
Aishu AnyShare missing authentication leaks user passwords in user API
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Do first: Workaround: The checked facts name no workaround or mitigation. Follow the vendor's own guidance until a fix is published.
Summary
AnyShare builds through 2024-11 contain a missing authentication vulnerability in the /api/ShareMgnt/Usrm_GetAllUsers endpoint that exposes user records including password fields. Attackers can send unauthenticated POST requests with a [start,limit] body to retrieve usernames, passwords, and department information for all users. Exploitation evidence was first observed by the Shadowserver Foundation on 2024-12-25.
Who should check
Teams running Shanghai Aishu AnyShare builds through 2024-11, including the /api/ShareMgnt/Usrm_GetAllUsers endpoint.
“AnyShare builds through 2024-11 contain a missing authentication vulnerability”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.7/10CVSS 8.7
- No patch5/5No patch listed yet
What would change the score
- Would score about 76 if added to CISA KEV
- Would score about 71 if CISA's SSVC rates exploitation active
- Would score about 36 if advisories confirm default setups are exposed
What to do
Workaround: The checked facts name no workaround or mitigation. Follow the vendor's own guidance until a fix is published.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2024-58403 (AnyShare Information Disclosure via Usrm_GetAllUsers Endpoint), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2024-58403 (entry last updated 2026-11-18):
Affected:
- Shanghai Aishu Information Technology Co., Ltd. AnyShare: through 2024-11
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- AnyShare builds through 2024-11 (source: https://www.vulncheck.com/advisories/anyshare-information-disclosure-via-usrm-getallusers-endpoint)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2024-58403 is not listed as of cve.now's last read.
This KEV status is for CVE-2024-58403 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/other/aishu-anyshare-info-exposure.yaml
- https://www.vulncheck.com/advisories/anyshare-information-disclosure-via-usrm-getallusers-endpoint
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2024-58403
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2024-58403"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- Shanghai Aishu Information Technology Co., Ltd. AnyShare
through 2024-11
Evidence 5
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2024-58403 |
| Record | NVD · CVE-2024-58403 |
| Public exploit code 2Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub). | |
| Exploit | cn-sec.com · archives/3431184.html |
| Repository | GitHub · projectdiscovery/nuclei-templates · http/vulnerabilities/other/aishu-anyshare-info-exposure.yaml |
| Other links 1 | |
| Link | vulncheck.com · advisories/anyshare-information-disclosure-via-usrm-getallusers-endpoint |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2024-58403
Is CVE-2024-58403 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The missing authentication flaw lets an unauthenticated attacker retrieve usernames, passwords, and department information for all users through the Usrm_GetAllUsers endpoint in AnyShare.Source: vulncheck.com
Which versions are affected by CVE-2024-58403?
AnyShare: through 2024-11.Source: cve.now feed data
Am I affected, and how do I check?
The record covers AnyShare builds through 2024-11, with no earlier lower bound listed. Compare your build's date against that 2024-11 cutoff to see which range it falls in.Source: vulncheck.com
How do I fix CVE-2024-58403?
The checked facts name no fixed version or vendor patch, so no upgrade target can be given. Check the vendor's advisory for a released fix.Source: vulncheck.com
What if there's no patch?
The checked facts name no workaround or mitigation. Follow the vendor's own guidance until a fix is published.Source: vulncheck.com