Skip to main content
CVE-2025-8372VulnerabilityPublished

CVE-2025-8372: code-projects Exam Form Submission · SQL Injection

Affects code-projects Exam Form SubmissionSource CVE Database V5

0

Not known to be exploited · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 08:30 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 39% 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 31 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
code-projects Exam Form SubmissionAffected
  • =1.0
Fixed in–

AI-suggested

1. Immediate mitigation should include restricting external access to the /admin/update_s7.php endpoint via network controls such as firewalls or VPNs, limiting exposure to trusted internal networks only. 2. Implement Web Application Firewall (WAF) rules to detect and block SQL injection patterns targeting the 'credits' parameter. 3. Conduct a thorough code review and apply parameterized queries or prepared statements to sanitize and validate all inputs, especially the 'credits' parameter in the update_s7.php script. 4. If possible, upgrade to a patched version once released by the vendor or apply community-provided patches after thorough testing. 5. Monitor logs for suspicious activities related to the vulnerable endpoint and unusual database queries. 6. Educate system administrators and developers about secure coding practices to prevent similar vulnerabilities. 7. Perform regular vulnerability scanning and penetration testing focusing on SQL injection vectors in the application. 8. Consider isolating the affected application in a segmented network zone to limit lateral movement in case of compromise.

Description

A vulnerability was found in code-projects Exam Form Submission 1.0 and classified as critical. Affected by this issue is some unknown functionality of the file /admin/update_s7.php. The manipulation of the argument credits leads to sql injection. The attack may be launched remotely. The exploit has been disclosed to the public and may be used.

References

Community reviews

Loading reviews…