Skip to main content
CVE-2025-6403VulnerabilityPublished Updated

CVE-2025-6403: code-projects School Fees Payment System · SQL Injection

Affects code-projects School Fees Payment SystemSource CVE Database V5

0

Not known to be exploited · public detection template (Nuclei) · 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
2.0% chance of exploitation in 30 days – higher than 80% 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 21 Jun 2025

  2. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  3. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  4. 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 School Fees Payment SystemAffected
  • =1.0
Fixed in–

AI-suggested

1. Immediate code review and input validation: Organizations should audit the /student.php file and any other input handling code to ensure strict validation and sanitization of all user-supplied inputs, especially the 'ID' parameter. Use parameterized queries or prepared statements to prevent SQL injection. 2. Implement Web Application Firewalls (WAFs): Deploy WAFs with rules specifically designed to detect and block SQL injection attempts targeting the vulnerable parameter. 3. Network segmentation and access controls: Restrict access to the payment system backend databases to only necessary services and users, minimizing the attack surface. 4. Monitor logs and alerts: Enable detailed logging of database queries and web requests to detect anomalous activities indicative of injection attempts. 5. Backup and recovery planning: Ensure regular backups of payment system databases are maintained and tested to enable rapid restoration in case of data corruption or deletion. 6. Vendor engagement: Contact the vendor for patches or updates and monitor for any forthcoming security advisories. 7. 8. Employee training: Educate administrative staff on recognizing suspicious system behavior and reporting potential incidents promptly.

Description

A vulnerability was found in code-projects School Fees Payment System 1.0. It has been rated as critical. This issue affects some unknown processing of the file /student.php. The manipulation of the argument ID 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…