CVE-2025-5729: code-projects Health Center Patient Record Management System · SQL Injection
Affects code-projects Health Center Patient Record Management SystemSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 33% 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:PExploitation evidence
Disclosed: evidence found.
CVE published 6 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| code-projects Health Center Patient Record Management System | Affected
| Fixed in– |
AI-suggested
Since no official patches are currently available, European healthcare organizations should immediately implement the following specific mitigations: 1) Conduct a thorough code review of the /birthing_record.php file and all input handling related to the 'itr_no' parameter to identify and fix SQL injection flaws by employing parameterized queries or prepared statements. 2) Apply Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection payloads targeting the vulnerable parameter. 3) Restrict database user permissions to the minimum necessary to limit the impact of any successful injection. 4) Monitor application logs and network traffic for unusual query patterns or access attempts to the vulnerable endpoint. 5) Isolate the affected system from external networks where possible until a patch is available. 6) Engage with the vendor or community for updates or patches and plan for timely application once released. 7) Conduct security awareness training for developers and administrators on secure coding practices and vulnerability management. These targeted actions go beyond generic advice by focusing on immediate containment and long-term remediation specific to this vulnerability and healthcare context.
Description
A vulnerability, which was classified as critical, was found in code-projects Health Center Patient Record Management System 1.0. Affected is an unknown function of the file /birthing_record.php. The manipulation of the argument itr_no leads to sql injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used.