Skip to main content
VulnerabilityPublished Updated

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

Affects NS-ASGSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 51% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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

Until an official patch is released, organizations should implement multiple layers of defense to mitigate CVE-2024-30862. First, deploy a web application firewall (WAF) with rules specifically designed to detect and block SQL Injection attempts targeting /3g/index.php. Conduct thorough input validation and sanitization on all user inputs interacting with the vulnerable endpoint, employing parameterized queries or prepared statements where possible. Restrict network access to the affected service to trusted IP ranges and segment the network to limit exposure. Monitor logs for unusual database query patterns or errors indicative of injection attempts. Apply the principle of least privilege to database accounts used by the application, ensuring they have only necessary permissions. Regularly review and update security policies and incident response plans to prepare for potential exploitation. Engage with netentsec support channels for updates on patches or official remediation guidance. Finally, consider deploying intrusion detection systems (IDS) tuned to detect SQL Injection signatures.

Description

netentsec NS-ASG 6.3 is vulnerable to SQL Injection via /3g/index.php.

References

Community reviews

Loading reviews…