Skip to main content
CVE-2025-10112VulnerabilityPublished

CVE-2025-10112: itsourcecode Student Information Management System · SQL Injection

Affects itsourcecode Student Information Management SystemSource CVE Database V5

0

Not known to be exploited · CVSS 6.9 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Sep 2025

  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 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
itsourcecode Student Information Management SystemAffected
  • =1.0
Fixed in–

AI-suggested

Since no official patches are currently available, European organizations should implement immediate compensating controls. These include: 1) Restricting network access to the vulnerable application by limiting inbound traffic to trusted IP addresses or VPNs; 2) Employing Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection patterns targeting the 'ID' parameter in /admin/modules/department/index.php; 3) Conducting thorough input validation and sanitization on all user-supplied parameters, especially 'ID', to prevent injection; 4) Monitoring application logs for suspicious query patterns or repeated failed attempts indicative of SQL injection probes; 5) Isolating the affected system within the network to minimize lateral movement; 6) Planning and prioritizing an upgrade or patch deployment once the vendor releases a fix; 7) Educating IT and security teams about the vulnerability and potential indicators of compromise. Additionally, organizations should review and enhance database user permissions to follow the principle of least privilege, limiting the damage potential of any successful injection.

Description

A weakness has been identified in itsourcecode Student Information Management System 1.0. The impacted element is an unknown function of the file /admin/modules/department/index.php. This manipulation of the argument ID causes sql injection. The attack is possible to be carried out remotely. The exploit has been made available to the public and could be exploited.

References

Community reviews

Loading reviews…