Skip to main content
VulnerabilityPublished Updated

CVE-2024-51211: My-CVE · SQL Injection

Affects My-CVESource CVE Database V5

0

Not known to be exploited · public detection template (Nuclei) · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
2.2% chance of exploitation in 30 days – higher than 82% 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 8 Nov 2024

  2. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

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

    Not in CISA KEV and no source reports exploitation

  4. 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
GitHubkutsa1/My-CVEpkg:github/kutsa1/My-CVEOther threatsAffected
  • =9.1
Fixed in–

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

AI-suggested

To mitigate CVE-2024-51211, organizations should immediately implement the following measures: 1) Apply input validation and sanitization on the $username_stn_id parameter by using prepared statements or parameterized queries to prevent SQL injection. 2) Deploy a Web Application Firewall (WAF) with rules specifically designed to detect and block SQL injection attempts targeting resetuserinfo.php and similar endpoints. 3) Restrict network access to the openSIS application to trusted IP ranges and enforce strong access controls. 4) Monitor logs for suspicious SQL query patterns or repeated failed attempts to exploit this parameter. 5) If possible, temporarily disable or restrict access to the resetuserinfo.php functionality until a vendor patch is released. 6) Engage with the vendor or community to obtain official patches or updates addressing this vulnerability. 7) Conduct security audits and penetration testing focused on SQL injection vectors in the application. These steps go beyond generic advice by focusing on the specific vulnerable parameter and endpoint, emphasizing proactive detection and access restriction.

Description

SQL injection vulnerability exists in OS4ED openSIS-Classic Version 9.1, specifically in the resetuserinfo.php file. The vulnerability is due to improper input validation of the $username_stn_id parameter, which can be manipulated by an attacker to inject arbitrary SQL commands.

References

Community reviews

Loading reviews…