Skip to main content
CVE-2025-8249VulnerabilityPublished

CVE-2025-8249: 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
GitHubdingzenggonpo/cvepkg:github/dingzenggonpo/cveOther threatsAffected
  • =1.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Given the absence of official patches, European organizations should immediately implement compensating controls. These include: 1) Restricting network access to the /admin/update_s3.php endpoint via firewall rules or web application firewalls (WAF) to allow only trusted IP addresses; 2) Employing input validation and sanitization at the application or proxy level to block malicious SQL payloads targeting the 'credits' parameter; 3) Monitoring logs for unusual or suspicious requests to the vulnerable endpoint; 4) Conducting code reviews and applying manual fixes to sanitize inputs if source code access is available; 5) Segregating the database with strict access controls and least privilege principles to limit damage if exploited; 6) Planning for an urgent upgrade or patch deployment once the vendor releases a fix; and 7) Educating IT staff about the vulnerability and signs of exploitation to enable rapid incident response.

Description

A vulnerability, which was classified as critical, has been found in code-projects Exam Form Submission 1.0. This issue affects some unknown processing of the file /admin/update_s3.php. The manipulation of the argument credits leads to sql injection. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used.

References

Community reviews

Loading reviews…