Skip to main content
CVE-2024-29432VulnerabilityPublished Updated

CVE-2024-29432: alldata · n/a

Affects alldataSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 43% 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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Apr 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
GitHubraybye/alldatapkg:github/raybye/alldataOther threatsAffected
  • =0.4.6
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Immediately restrict access to the /data/masterdata/datas endpoint, limiting it to trusted internal networks or VPNs. 2. Implement strict input validation and sanitization on the 'tablename' parameter, ensuring only expected table names or patterns are accepted. 3. Use parameterized queries or prepared statements in the application code to prevent SQL injection. 4. Deploy a web application firewall (WAF) with rules to detect and block SQL injection attempts targeting this endpoint. 5. Monitor logs for suspicious activity related to the 'tablename' parameter and unusual database queries. 6. Engage with the Alldata vendor or community to obtain patches or updates as soon as they become available. 7. Conduct a thorough security review of other input parameters and endpoints to identify similar injection risks. 8. Educate developers and administrators about secure coding practices and the risks of SQL injection.

Description

Alldata v0.4.6 was discovered to contain a SQL injection vulnerability via the tablename parameter at /data/masterdata/datas.

References

Community reviews

Loading reviews…