CVE-2025-5627VulnerabilityPublished 5 Jun 2025

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

Affects code-projects 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

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

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

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 5 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
code-projects Patient Record Management System	Affected =1.0	Fixed in–

AI-suggested

Organizations should immediately audit their deployments of the code-projects Patient Record Management System version 1.0 to identify exposure to the /sputum_form.php endpoint. As no official patches are currently available, mitigation should focus on implementing web application firewall (WAF) rules to detect and block SQL injection patterns targeting the 'itr_no' parameter. Input validation and parameterized queries or prepared statements should be enforced at the application level to sanitize inputs rigorously. Network segmentation and access controls should limit exposure of the vulnerable system to untrusted networks. Monitoring and logging of database queries and web application logs should be enhanced to detect anomalous activities indicative of exploitation attempts. Organizations should also prepare for rapid patch deployment once a fix is released and consider alternative patient record management solutions if remediation is delayed. Regular security assessments and penetration testing focusing on injection flaws are recommended to proactively identify similar vulnerabilities.

Description

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

Impact

For European organizations, especially healthcare providers using the affected Patient Record Management System, this vulnerability poses a significant risk to patient data confidentiality and integrity. Exploitation could lead to unauthorized disclosure of sensitive personal health information, violating GDPR and other data protection regulations, potentially resulting in legal penalties and reputational damage. Data integrity could be compromised, affecting clinical decisions and patient safety. Availability impact appears limited but cannot be ruled out if attackers manipulate or delete critical records. The remote and unauthenticated nature of the attack vector increases the likelihood of exploitation, potentially enabling attackers to access or manipulate data without detection. Given the critical role of healthcare systems in Europe, any compromise could disrupt healthcare services and erode trust in digital health infrastructure.

Summary

CVE-2025-5627 is a SQL Injection vulnerability identified in version 1.0 of the code-projects Patient Record Management System, specifically within the /sputum_form.php file. The vulnerability arises from improper sanitization or validation of the 'itr_no' parameter, which an attacker can manipulate to inject malicious SQL code. This injection flaw allows an unauthenticated remote attacker to execute arbitrary SQL commands on the backend database. Although the exact database type is unspecified, exploitation could lead to unauthorized data access, data modification, or even deletion. The vulnerability does not require user interaction or authentication, increasing its risk profile. The CVSS 4.0 base score is 5.3, indicating a medium severity level, reflecting limited impact on confidentiality, integrity, and availability, and the presence of some privileges required (PR:L). No known exploits are currently reported in the wild, and no patches have been published yet. The vulnerability's presence in a patient record management system is particularly concerning due to the sensitive nature of healthcare data involved.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 7 Jul 2025, 03:24 UTC

Technical details

References

Community reviews

Related threats