Skip to main content
VulnerabilityPublished

CVE-2025-8371: 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.5% chance of exploitation in 30 days – higher than 46% 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

European organizations should immediately audit their environments to identify any deployments of code-projects Exam Form Submission version 1.0. In the absence of official patches, the following specific mitigations are recommended: 1) Implement Web Application Firewall (WAF) rules to detect and block SQL injection patterns targeting the 'credits' parameter in /admin/update_s5.php. 2) Restrict network access to the administrative interface by IP whitelisting or VPN-only access to reduce exposure to remote attackers. 3) Employ input validation and parameterized queries at the application level if source code access is available, to sanitize the 'credits' parameter and prevent injection. 4) Monitor database logs and application logs for unusual queries or errors indicative of injection attempts. 5) Conduct penetration testing focused on SQL injection vectors to verify the effectiveness of mitigations. 6) Prepare an incident response plan for potential data breaches involving this vulnerability. 7) Engage with the vendor or community for updates or patches and plan for timely application once available. These targeted actions go beyond generic advice by focusing on the specific vulnerable parameter and attack vector.

Description

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

References

Community reviews

Loading reviews…