CVE-2024-30863: NS-ASG · SQL Injection
Affects NS-ASGSource CVE Database V5
Not known to be exploited · CVSS 6.3 Medium.
Data as of 26 Oct 2026, 14:05 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:H/PR:L/UI:N/S:C/C:N/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 1 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 |
|---|---|---|
GitHubhundanchen69/NS-ASGpkg:github/hundanchen69/NS-ASGOther 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
- Implement strict input validation and sanitization on all parameters accepted by /WebPages/history.php to prevent injection of malicious SQL code.
- Employ parameterized queries or prepared statements in the application code to eliminate direct concatenation of user input into SQL commands.
- Restrict database user permissions to the minimum necessary, ensuring the application account cannot perform unauthorized data modifications.
- Monitor database logs and web server logs for unusual query patterns or repeated failed attempts indicative of injection attempts.
- If possible, isolate the affected web interface behind network segmentation or access controls to limit exposure.
- Engage with netentsec support or vendor channels to obtain patches or official remediation guidance as soon as they become available.
- Conduct regular security assessments and code reviews focusing on input handling in web applications.
- Educate developers and administrators about secure coding practices related to SQL Injection prevention.
- Consider deploying Web Application Firewalls (WAFs) with rules tuned to detect and block SQL Injection attempts targeting the vulnerable endpoint.
- Maintain an incident response plan to quickly address any signs of exploitation.
Description
netentsec NS-ASG 6.3 is vulnerable to SQL Injection via /WebPages/history.php.