CVE-2025-63512VulnerabilityPublished 18 Nov 2025

CVE-2025-63512: n/a

Source CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

6.5Medium

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

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: None

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

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, 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: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
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 impacted component.
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 on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

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

AI-suggested

To mitigate CVE-2025-63512, organizations should immediately review and update the affected Hospital Management System code to implement parameterized queries or prepared statements in place of dynamic SQL concatenation, particularly for the 'demail' parameter in admin-panel1.php. Input validation should be enforced to restrict inputs to expected formats, such as valid email addresses, reducing injection risk. If source code modification is not immediately feasible, deploying a Web Application Firewall (WAF) with rules targeting SQL Injection patterns can provide temporary protection. Restrict network access to the admin panel by implementing IP whitelisting or VPN-only access to reduce exposure. Database user accounts used by the application should have the least privileges necessary, preventing unauthorized data manipulation beyond what is required. Regularly audit database logs for suspicious queries indicative of injection attempts. Organizations should also conduct security assessments and penetration testing focused on injection vulnerabilities in all web-facing applications. Finally, maintain an inventory of all hospital management software versions in use to identify and prioritize vulnerable instances for patching or replacement. Coordination with software vendors for official patches or updates is recommended once available.

Description

CVE-2025-63512 is a medium-severity SQL Injection vulnerability found in the kishan0725 Hospital Management System v4, specifically in the admin-panel1.php file within the deleting doctor functionality. The vulnerability arises because the application does not properly sanitize or parameterize the 'demail' parameter before using it in a dynamic SQL query. This flaw allows unauthenticated remote attackers to inject malicious SQL commands, potentially leading to unauthorized data access or modification. Although no known exploits are currently reported in the wild, exploitation could compromise the confidentiality and integrity of sensitive healthcare data. The vulnerability requires no authentication or user interaction and can be exploited remotely over the network. European healthcare organizations using this system are at risk, especially those with limited security controls around legacy or niche hospital management software. Mitigation involves applying secure coding practices such as prepared statements and input validation, and monitoring for suspicious database activity. Countries with significant healthcare infrastructure and adoption of such systems, including Germany, France, Italy, Spain, and the UK, are most likely to be affected. Given the potential impact on sensitive patient data and ease of exploitation, timely remediation is critical.

Impact

The primary impact of CVE-2025-63512 on European organizations lies in the potential compromise of sensitive healthcare data managed by the affected Hospital Management System. Successful exploitation could lead to unauthorized disclosure of patient information, violating data protection regulations such as GDPR, and damaging organizational reputation. Integrity of medical records could also be undermined, potentially affecting patient care and safety. Although availability is not directly impacted, the downstream effects of data corruption or breach investigations could disrupt hospital operations. The vulnerability requires no authentication and can be exploited remotely, increasing the risk of widespread attacks, especially in environments with exposed administrative interfaces. European healthcare providers using this system or similar legacy software with insufficient input validation are at heightened risk. The breach of confidential health data could also lead to regulatory fines and legal consequences under European data protection laws. Furthermore, attackers might leverage this vulnerability as an initial foothold for further network intrusion or ransomware deployment, compounding the impact. Overall, the threat poses a significant risk to the confidentiality and integrity of critical healthcare information systems in Europe.

Summary

CVE-2025-63512 identifies a SQL Injection vulnerability in the kishan0725 Hospital Management System version 4, specifically within the admin-panel1.php script's deleting doctor logic. The vulnerability stems from improper handling of the 'demail' parameter, which is incorporated directly into a dynamic SQL query without adequate sanitization or use of parameterized queries. This allows an unauthenticated attacker to craft malicious input that alters the intended SQL command, potentially enabling unauthorized reading or modification of the underlying database. The vulnerability is classified under CWE-89 (Improper Neutralization of Special Elements used in an SQL Command). The CVSS v3.1 base score is 6.5, reflecting a medium severity level with network attack vector, low attack complexity, no privileges required, and no user interaction needed. The impact primarily affects confidentiality and integrity, with no direct effect on availability. No patches or fixes are currently linked, and no known exploits have been reported in the wild. The vulnerability's presence in a hospital management system is particularly concerning due to the sensitive nature of healthcare data, including patient records and operational information. Exploitation could lead to data leakage, unauthorized data manipulation, or further compromise of the hospital's IT environment. The lack of authentication requirements and ease of remote exploitation increase the urgency for remediation. Organizations using this system should prioritize code review and implement parameterized queries or stored procedures to prevent SQL Injection. Additionally, monitoring database logs for anomalous queries and restricting database user permissions can help mitigate risk.

CWE-89Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #2OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design · Parameterization
If available, use structured mechanisms that automatically enforce the separation between data and code. These mechanisms may be able to provide the relevant quoting, encoding, and validation automatically, instead of relying on the developer to provide this capability at every point where output is generated.
Architecture and Design · Operation · Environment Hardening
Run your code using the lowest privileges that are required to accomplish the necessary tasks. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment.
OWASP Cheat Sheets
Query Parameterization (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
XML Security (opens in a new tab)
XML External Entity Prevention (opens in a new tab)
File Upload (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.4 (opens in a new tab)
V5.3.5 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
Command Line Execution through SQL Injection (opens in a new tab)
Object Relational Mapping Injection (opens in a new tab)
SQL Injection through SOAP Parameter Tampering (opens in a new tab)
Expanding Control over the Operating System from the Database (opens in a new tab)
SQL Injection (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/NicatAliyevh/Zero-Days/blob/main/Hospital_Management_System_SQL2.md (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 25 Nov 2025, 17:16 UTC

WeaknessesCWE-89

Technical details

References

Community reviews

Related threats