Skip to main content
CVE-2025-5971VulnerabilityPublished

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

Affects code-projects School Fees Payment SystemSource CVE Database V5

0

Not known to be exploited · CVSS 5.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 49% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Jun 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 School Fees Payment SystemAffected
  • =1.0
Fixed in–

AI-suggested

1. Immediate network-level controls: Restrict external access to the School Fees Payment System, especially the /ajx.php endpoint, using firewalls or web application firewalls (WAFs) with rules to detect and block SQL injection patterns targeting the 'name_startsWith' parameter. 2. Input validation and sanitization: Developers should implement strict input validation and parameterized queries or prepared statements to prevent SQL injection in the affected codebase. 3. System isolation: Segregate the payment system from other critical infrastructure and sensitive data stores to limit lateral movement in case of compromise. 4. Monitoring and detection: Deploy intrusion detection systems (IDS) and log analysis focusing on anomalous database queries or repeated access attempts to the vulnerable parameter. 5. Incident response readiness: Prepare to respond to potential data breaches by having backup data, forensic capabilities, and communication plans in place. 6. Vendor engagement: Engage with the vendor or community maintaining the code-projects system to obtain or develop patches or updates addressing this vulnerability. 7. Temporary mitigations: If patching is not immediately possible, consider disabling or restricting the vulnerable functionality until a fix is available.

Description

A vulnerability was found in code-projects School Fees Payment System 1.0. It has been classified as critical. This affects an unknown part of the file /ajx.php. The manipulation of the argument name_startsWith leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.

References

Community reviews

Loading reviews…