CVE-2025-13243: code-projects Student Information System · SQL Injection
Affects code-projects Student Information SystemSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 31% 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 16 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-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubasd1238525/cvepkg:github/asd1238525/cveOther 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. Monitor vendor communications closely and apply official patches or updates as soon as they become available to address CVE-2025-13243. 2. Implement strict input validation and sanitization on all user inputs, especially in the /editprofile.php module, to prevent malicious SQL code injection. 3. Employ the principle of least privilege by restricting database user permissions to only those necessary for application functionality, minimizing potential damage from exploitation. 4. Use Web Application Firewalls (WAFs) configured to detect and block SQL injection attempts targeting the Student Information System. 5. Conduct regular security audits and code reviews focusing on input handling and database queries within the application. 6. Segment the network to isolate the Student Information System from other critical systems to limit lateral movement in case of compromise. 7. Educate system administrators and users about the risks and signs of SQL injection attacks to improve detection and response. 8. Maintain comprehensive logging and monitoring to detect anomalous database queries or unauthorized access attempts promptly.
Description
A vulnerability was found in code-projects Student Information System 2.0. Impacted is an unknown function of the file /editprofile.php. The manipulation results in sql injection. The attack may be performed from remote. The exploit has been made public and could be used.