CVE-2024-27602: Alldata · Improper Access Control
Affects AlldataSource CVE Database V5
Not known to be exploited · CVSS 9.1 Critical.
Data as of 26 Oct 2026, 13:47 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 2 Apr 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHuballdata/Alldatapkg:github/alldata/AlldataOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
- Immediately restrict access to the /api/system/v2/api-docs endpoint and any other API documentation interfaces by implementing strong authentication and authorization controls, ensuring only authorized personnel can access these resources.
- Deploy network-level access controls such as IP whitelisting or VPN requirements to limit exposure of sensitive API endpoints to trusted networks.
- Implement Web Application Firewalls (WAFs) with custom rules to detect and block unauthorized requests targeting API documentation paths.
- Conduct thorough audits of all API endpoints to identify and secure any other improperly exposed interfaces.
- Monitor logs and network traffic for unusual access patterns or repeated requests to API documentation endpoints, enabling early detection of exploitation attempts.
- Engage with the vendor or community to obtain patches or updates addressing this vulnerability as soon as they become available.
- Consider temporary disabling or removing API documentation endpoints from production environments until secure access controls are enforced.
- Educate development and operations teams on secure API exposure practices to prevent similar issues in future releases.
Description
Alldata V0.4.6 is vulnerable to Incorrect Access Control. A total of many modules interface documents have been leaked.For example, the /api/system/v2/api-docs module.