CVE-2025-13581: itsourcecode Student Information System · SQL Injection
Affects itsourcecode Student Information SystemSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 26% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:PExploitation evidence
Disclosed: evidence found.
CVE published 24 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
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
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-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| itsourcecode Student Information System | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2025-13581, organizations should immediately implement input validation and sanitization on the schedule_id parameter to prevent SQL injection. Employing parameterized queries or prepared statements is critical to ensure that user input cannot alter SQL command structure. If source code modification is not feasible, deploying a Web Application Firewall (WAF) with specific rules to detect and block SQL injection attempts targeting /schedule_edit1.php can provide a temporary safeguard. Restricting access to the vulnerable endpoint by IP whitelisting or VPN access can reduce exposure. Regularly monitoring logs for suspicious query patterns or repeated access attempts to schedule_edit1.php will aid in early detection of exploitation attempts. Organizations should also inventory their software versions to identify affected instances and prioritize updates or migration to newer, patched versions once available. Finally, conducting security awareness training for administrators on the risks of SQL injection and ensuring secure coding practices in future development will help prevent recurrence.
Description
A vulnerability was identified in itsourcecode Student Information System 1.0. Affected by this vulnerability is an unknown functionality of the file /schedule_edit1.php. Such manipulation of the argument schedule_id leads to sql injection. The attack may be launched remotely. The exploit is publicly available and might be used.