Skip to main content
VulnerabilityPublished Updated

CVE-2024-30863: NS-ASG · SQL Injection

Affects NS-ASGSource CVE Database V5

0

Not known to be exploited · CVSS 6.3 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.
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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubhundanchen69/NS-ASGpkg:github/hundanchen69/NS-ASGOther threatsAffected
  • =6.3
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. Implement strict input validation and sanitization on all parameters accepted by /WebPages/history.php to prevent injection of malicious SQL code.
  2. Employ parameterized queries or prepared statements in the application code to eliminate direct concatenation of user input into SQL commands.
  3. Restrict database user permissions to the minimum necessary, ensuring the application account cannot perform unauthorized data modifications.
  4. Monitor database logs and web server logs for unusual query patterns or repeated failed attempts indicative of injection attempts.
  5. If possible, isolate the affected web interface behind network segmentation or access controls to limit exposure.
  6. Engage with netentsec support or vendor channels to obtain patches or official remediation guidance as soon as they become available.
  7. Conduct regular security assessments and code reviews focusing on input handling in web applications.
  8. Educate developers and administrators about secure coding practices related to SQL Injection prevention.
  9. Consider deploying Web Application Firewalls (WAFs) with rules tuned to detect and block SQL Injection attempts targeting the vulnerable endpoint.
  10. 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.

References

Community reviews

Loading reviews…