Skip to main content
CVE-2025-13240VulnerabilityPublished Updated

CVE-2025-13240: code-projects Student Information System · SQL Injection

Affects code-projects Student Information 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 40% 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 16 Nov 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
code-projects Student Information SystemAffected
  • =2.0
Fixed in–

AI-suggested

1. Immediately audit all instances of code-projects Student Information System version 2.0 to identify vulnerable deployments. 2. Implement input validation and sanitization for the 's' parameter in /searchquery.php, ensuring only expected input formats are accepted. 3. Refactor database queries to use parameterized statements or prepared queries to prevent SQL injection. 4. Deploy Web Application Firewalls (WAFs) with rules specifically targeting SQL injection patterns related to this vulnerability. 5. Monitor database logs and application logs for unusual query patterns or errors indicative of injection attempts. 6. Restrict database user permissions to the minimum necessary to limit the impact of a successful injection. 7. Educate development and IT teams about secure coding practices and the importance of patching known vulnerabilities. 8. Engage with the vendor or community to obtain or develop official patches or updates. 9. Conduct penetration testing focused on injection flaws to verify remediation effectiveness. 10. Prepare incident response plans to quickly address any exploitation attempts.

Description

A vulnerability was detected in code-projects Student Information System 2.0. This affects an unknown part of the file /searchquery.php. Performing manipulation of the argument s results in sql injection. Remote exploitation of the attack is possible. The exploit is now public and may be used.

References

Community reviews

Loading reviews…