Skip to main content
CVE-2025-7191VulnerabilityPublished

CVE-2025-7191: code-projects Student Enrollment System · SQL Injection

Affects code-projects Student Enrollment SystemSource CVE Database V5

0

Not known to be exploited · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 06:26 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 41% 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 Jul 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-26.

What to do

Affected software

ProductAffectedFixed in
code-projects Student Enrollment SystemAffected
  • =1.0
Fixed in–

AI-suggested

1. Immediate implementation of input validation and parameterized queries or prepared statements in the /login.php file to prevent SQL injection attacks. 2. Conduct a thorough code review of the entire Student Enrollment System to identify and remediate any other injection points or security weaknesses. 3. If vendor patches become available, prioritize their deployment across all affected systems. 4. Employ Web Application Firewalls (WAFs) configured to detect and block SQL injection attempts targeting the login endpoint. 5. Monitor logs for unusual login attempts or database errors indicative of injection attempts. 6. Restrict database user permissions to the minimum necessary to limit the impact of a potential injection attack. 7. Consider migrating to a more secure and actively maintained enrollment system if remediation is not feasible. 8. Educate IT staff and administrators on the risks of SQL injection and the importance of secure coding practices.

Description

A vulnerability has been found in code-projects Student Enrollment System 1.0 and classified as critical. This vulnerability affects unknown code of the file /login.php. The manipulation of the argument Username leads to sql injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used.

References

Community reviews

Loading reviews…