Skip to main content
CVE-2025-8250VulnerabilityPublished

CVE-2025-8250: 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 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.5% chance of exploitation in 30 days – higher than 45% 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 28 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-25.

What to do

Affected software

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

AI-suggested

Given the absence of official patches, European organizations should implement immediate compensating controls. These include deploying web application firewalls (WAFs) with custom rules to detect and block SQL injection patterns targeting the 'credits' parameter in /admin/update_s4.php. Network segmentation should be enforced to restrict access to the administrative interface to trusted internal IP addresses only. Input validation and sanitization should be reviewed and enhanced in the application codebase, prioritizing the use of parameterized queries or prepared statements to prevent SQL injection. Organizations should conduct thorough code audits and penetration testing to identify similar vulnerabilities. Monitoring and logging of database queries and web server access should be intensified to detect anomalous activities indicative of exploitation attempts. Finally, organizations should prepare for rapid patch deployment once an official fix is released and consider isolating or disabling the vulnerable module if feasible until remediation is available.

Description

A vulnerability, which was classified as critical, was found in code-projects Exam Form Submission 1.0. Affected is an unknown function of the file /admin/update_s4.php. The manipulation of the argument credits leads to sql injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used.

References

Community reviews

Loading reviews…