VulnerabilityPublished 3 Sep 2025Updated 16 Dec 2025

CVE-2025-45805: phpgurukul Doctor Appointment Management System · Cross-site Scripting

Source CVE Database V5

Not known to be exploited · CVSS 7.6 High.

Data as of 26 Oct 2026, 11:42 UTC

CVSS 3.1 base score

7.6High

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

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

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

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

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: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
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: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
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: 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 impacted component 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 impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 3 Sep 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 26 Oct 2026.

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 or the CVSS exploit maturity 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-45805, organizations should implement strict input validation and output encoding on all user-supplied data, especially fields like the doctor’s profile name. Employ context-aware encoding (e.g., HTML entity encoding) to neutralize any injected scripts before rendering. Use security libraries or frameworks that automatically handle XSS protections. Conduct thorough code reviews and penetration testing focused on injection flaws. Deploy a Web Application Firewall (WAF) with rules to detect and block malicious JavaScript payloads targeting profile fields. Restrict doctor user privileges to minimize injection opportunities and monitor logs for suspicious input patterns. Educate developers on secure coding practices aligned with OWASP guidelines. If possible, isolate the appointment booking interface to limit script execution impact. Regularly update and patch the system once vendor fixes become available. Additionally, implement Content Security Policy (CSP) headers to reduce the risk of script execution from untrusted sources. Finally, ensure incident response plans are prepared to quickly address any exploitation attempts.

Description

CVE-2025-45805 is a high-severity stored cross-site scripting (XSS) vulnerability in the phpgurukul Doctor Appointment Management System 1.0. An authenticated doctor user can inject arbitrary JavaScript code into their profile name, which is then rendered unsanitized when other users view the doctor’s profile to book appointments. This vulnerability allows attackers to execute malicious scripts in the context of other users’ browsers, potentially leading to session hijacking, data theft, or further exploitation. The CVSS score is 7.6, indicating a high impact with network attack vector and low attack complexity. No known exploits are currently reported in the wild. European healthcare organizations using this system could face confidentiality breaches and service disruptions. Mitigation requires implementing proper input validation and output encoding on user-supplied data, especially profile fields. Countries with significant healthcare IT adoption and use of PHP-based appointment systems, such as Germany, France, and the UK, are most likely to be affected.

Impact

For European organizations, particularly healthcare providers using the phpgurukul Doctor Appointment Management System, this vulnerability can lead to serious confidentiality breaches. Attackers exploiting this XSS flaw could steal session cookies or authentication tokens from patients or staff, leading to unauthorized access to personal health information (PHI). This compromises patient privacy and violates GDPR regulations, potentially resulting in heavy fines and reputational damage. Additionally, attackers could manipulate appointment bookings or inject malicious content, disrupting healthcare services and undermining trust in digital health platforms. The vulnerability also increases the attack surface for further exploitation, such as pivoting to internal networks or deploying ransomware. Given the critical nature of healthcare operations, even limited integrity or availability impact can have severe consequences. The threat is heightened in environments where multiple users access the system concurrently, increasing the likelihood of malicious script execution. Overall, the vulnerability poses a high risk to confidentiality and moderate risk to integrity and availability within European healthcare contexts.

CWE-79Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #1OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
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.
Implementation · Architecture and Design
Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages.
Architecture and Design · Implementation · Attack Surface Reduction
Understand all the potential areas where untrusted inputs can enter your software: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide…
OWASP Cheat Sheets
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Injection Prevention (opens in a new tab)
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.3 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
XSS Using MIME Type Mismatch (opens in a new tab)
DOM-Based XSS (opens in a new tab)
Reflected XSS (opens in a new tab)
Stored XSS (opens in a new tab)
Cross-Site Scripting (XSS) (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 23 Dec 2025, 17:23 UTC

WeaknessesCWE-79

Technical details

References

Community reviews

Related threats