CVE-2024-33787: n/a
Source CVE Database V5
Not known to be exploited · CVSS 8.2 High.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 36% 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:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 3 May 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 2026-10-25.
What to do
AI-suggested
1. Apply official patches or updates from the vendor as soon as they become available to address the SQL injection vulnerability directly. 2. In the absence of patches, implement strict input validation on the tuser_Number parameter to allow only expected input formats (e.g., numeric or alphanumeric constraints). 3. Use parameterized queries or prepared statements in the backend code to prevent SQL injection attacks by separating code from data. 4. Restrict database user permissions to the minimum necessary, avoiding elevated privileges that could be exploited through injection. 5. Employ web application firewalls (WAFs) with rules designed to detect and block SQL injection attempts targeting the vulnerable parameter. 6. Conduct regular security assessments and code reviews focusing on input handling and database interactions. 7. Monitor logs for unusual query patterns or repeated failed attempts to exploit the vulnerability. 8. Segment and isolate the affected platform within the network to limit exposure to untrusted sources. 9. Educate developers and administrators about secure coding practices and the risks of SQL injection.
Description
Hengan Weighing Management Information Query Platform 2019-2021 53.25 was discovered to contain a SQL injection vulnerability via the tuser_Number parameter at search_user.aspx.