Skip to main content
CVE-2025-5857VulnerabilityPublished

CVE-2025-5857: code-projects Patient Record Management System · SQL Injection

Affects code-projects Patient Record Management SystemSource CVE Database V5

0

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 39% 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 9 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
code-projects Patient Record Management SystemAffected
  • =1.0
Fixed in–

AI-suggested

Since no official patches are currently available, European organizations should take immediate steps to mitigate risk. First, restrict network access to the Patient Record Management System to trusted internal networks and VPNs only, minimizing exposure to remote attackers. Implement Web Application Firewalls (WAFs) with rules designed to detect and block SQL injection attempts targeting the 'itr_no' parameter or the /urinalysis_record.php endpoint. Conduct thorough input validation and sanitization on all user inputs, especially the 'itr_no' parameter, using parameterized queries or prepared statements if possible. Monitor logs for suspicious SQL query patterns or repeated failed attempts to access the vulnerable endpoint. If feasible, upgrade or migrate to a newer, patched version of the software or an alternative solution. Additionally, conduct security awareness training for IT staff to recognize and respond to potential exploitation attempts. Regular backups of patient data should be maintained to ensure recovery in case of data integrity compromise.

Description

A vulnerability was found in code-projects Patient Record Management System 1.0 and classified as critical. This issue affects some unknown processing of the file /urinalysis_record.php. The manipulation of the argument itr_no 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…