Skip to main content
VulnerabilityPublished

CVE-2025-5674: 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, 14:05 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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 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

  1. Immediate mitigation should include implementing web application firewall (WAF) rules to detect and block SQL injection attempts targeting the 'urinalysis_id' parameter.
  2. Conduct a thorough code review and apply input validation and parameterized queries or prepared statements to sanitize all user inputs, especially the 'urinalysis_id' parameter.
  3. Isolate or segment the Patient Record Management System within the network to limit exposure to external threats.
  4. Monitor logs for suspicious database query patterns indicative of injection attempts.
  5. Engage with the vendor or community to obtain or develop patches or updates addressing this vulnerability.
  6. Where possible, restrict access to the vulnerable functionality to authenticated and authorized users, even though the vulnerability does not require authentication, to reduce attack surface.
  7. Educate IT and security teams about this vulnerability and ensure incident response plans include scenarios involving SQL injection attacks on healthcare systems.
  8. Consider temporary disabling or restricting access to the urinalysis_form.php functionality if it is not critical until a patch is available.

Description

A vulnerability was found in code-projects Patient Record Management System 1.0 and classified as critical. Affected by this issue is some unknown functionality of the file urinalysis_form.php. The manipulation of the argument urinalysis_id leads to sql injection. The attack may be launched remotely. The exploit has been disclosed to the public and may be used.

References

Community reviews

Loading reviews…