CVE-2025-7604VulnerabilityPublished 14 Jul 2025

CVE-2025-7604: PHPGurukul Hospital Management System · SQL Injection

Affects PHPGurukul Hospital Management SystemSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

6.9Medium

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

EPSS: 0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
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

Threat metrics

Exploit Maturity: POC

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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
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.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 14 Jul 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-26.

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
PHPGurukul Hospital Management System	Affected =4.0	Fixed in–

AI-suggested

Immediate mitigation steps include implementing strict input validation and parameterized queries or prepared statements in the /user-login.php script to prevent SQL injection. Organizations should conduct a thorough code review of the login module and related database interactions to identify and remediate similar vulnerabilities. Until an official patch is released by PHPGurukul, deploying Web Application Firewalls (WAFs) with SQL injection detection and prevention rules can help block exploitation attempts. Monitoring login activity for unusual patterns and implementing multi-factor authentication (MFA) can reduce the risk of unauthorized access. Regular backups of the database and system configurations should be maintained to enable recovery in case of compromise. Additionally, healthcare providers should engage with PHPGurukul support channels to obtain updates or patches promptly and consider isolating or restricting network access to the affected HMS instance to trusted internal networks only.

Description

A vulnerability was found in PHPGurukul Hospital Management System 4.0. It has been declared as critical. Affected by this vulnerability is an unknown functionality of the file /user-login.php. The manipulation of the argument Username 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, particularly hospitals and healthcare providers using PHPGurukul HMS 4.0, this vulnerability could lead to severe data breaches involving patient personal and medical information, violating GDPR and other data protection regulations. Unauthorized database access could disrupt hospital operations, compromise patient safety, and damage organizational reputation. The ability to manipulate login credentials or escalate privileges could allow attackers to gain persistent access, further endangering system integrity and availability. Given the critical role of hospital management systems in patient care, exploitation could also indirectly impact healthcare delivery and emergency response. The medium CVSS score suggests a moderate but tangible risk, especially as healthcare data is a high-value target for cybercriminals and ransomware groups. European healthcare institutions must consider this vulnerability a priority due to the sensitive nature of the data and the potential regulatory and operational consequences.

Summary

CVE-2025-7604 is a critical SQL Injection vulnerability identified in version 4.0 of the PHPGurukul Hospital Management System (HMS). The vulnerability exists in the /user-login.php file, specifically in the handling of the 'Username' parameter. An attacker can remotely exploit this flaw by manipulating the Username input to inject malicious SQL code. This allows unauthorized access to the underlying database, potentially enabling attackers to extract sensitive patient and hospital data, modify records, or escalate privileges within the system. The vulnerability requires no authentication or user interaction, making it highly accessible for remote exploitation. The CVSS 4.0 base score is 6.9 (medium severity), reflecting the vulnerability's ease of exploitation (network attack vector, low attack complexity, no privileges or user interaction required) but with limited impact on confidentiality, integrity, and availability (low to limited impact). Given the critical nature of hospital management systems in handling sensitive health data and operational workflows, this vulnerability poses a significant threat to healthcare providers using PHPGurukul HMS 4.0.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 14 Jul 2025, 13:01 UTC

Technical details

References

Community reviews

Related threats