CVE-2025-11551: code-projects Student Result Manager · SQL Injection
Affects code-projects Student Result ManagerSource 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 33% 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 9 Oct 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 |
|---|---|---|
| code-projects Student Result Manager | Affected
| Fixed in– |
AI-suggested
1. Conduct an immediate code audit focusing on the src/students/Database.java file to identify and isolate vulnerable SQL query constructions. 2. Refactor all database access code to use parameterized queries or prepared statements to eliminate direct concatenation of user inputs. 3. Implement strict input validation and sanitization for all parameters, especially roll, name, and gpa fields, enforcing type, length, and format constraints. 4. Restrict database user permissions to the minimum necessary to limit the impact of potential exploitation. 5. Monitor application logs and database access patterns for unusual queries or anomalies indicative of SQL injection attempts. 6. If possible, deploy Web Application Firewalls (WAFs) with SQL injection detection rules tailored to the application’s query patterns. 7. Engage with the vendor or development community to obtain or develop official patches or updates addressing this vulnerability. 8. Educate developers and administrators on secure coding practices to prevent similar vulnerabilities in future releases. 9. Isolate or segment the application environment to limit lateral movement in case of compromise. 10. Prepare incident response plans specific to data breaches involving student data to ensure rapid containment and notification.
Description
A vulnerability was determined in code-projects Student Result Manager 1.0. This affects an unknown function of the file src/students/Database.java. This manipulation of the argument roll/name/gpa causes sql injection. It is possible to initiate the attack remotely. The exploit has been publicly disclosed and may be utilized.