CVE-2024-46626: openSIS-Classic · n/a
Affects openSIS-ClassicSource CVE Database V5
Not known to be exploited · public exploit available (Exploit-DB) · CVSS 8.8 High.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.8% chance of exploitation in 30 days – higher than 58% 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:HExploitation evidence
t = 0 is the CVE’s publication on cve.org
Disclosed: evidence found.
CVE published 2 Oct 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
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
Timeline
CVE ID reserved
by mitre
, 21 days before disclosure
First Exploit-DB entry (opens in a new tab)
openSIS 9.1 - SQLi (Authenticated)
, 1 day before disclosure
CVE published
on cve.org
, t = 0
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
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubd0ub1edd/openSIS-Classicpkg:github/d0ub1edd/openSIS-ClassicOther 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
1. Immediately conduct a thorough audit of all openSIS-Classic v9.1 deployments to identify vulnerable instances. 2. Implement network-level access controls to restrict access to openSIS management interfaces to trusted IP addresses only. 3. Employ Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection payloads targeting openSIS. 4. Review and harden database permissions to minimize the impact of potential SQL injection attacks, ensuring the application uses least privilege principles. 5. Monitor logs for unusual SQL query patterns or errors indicative of injection attempts. 6. Engage with OS4ED or openSIS maintainers for timely patch releases and apply updates as soon as they become available. 7. Consider deploying database activity monitoring tools to detect and alert on suspicious queries in real time. 8. Educate system administrators and security teams about this vulnerability and the importance of rapid response. 9. If feasible, isolate openSIS systems in segmented network zones to limit lateral movement in case of compromise. 10. Prepare incident response plans specifically addressing SQL injection exploitation scenarios.
Description
OS4ED openSIS-Classic v9.1 was discovered to contain a SQL injection vulnerability via a crafted payload.