CVE-2025-63527: Blood Bank Management System · Cross-site Scripting
Source CVE Database V5
Not known to be exploited · CVSS 8.5 High.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AC:L/AV:N/A:N/C:H/I:L/PR:L/S:C/UI:NExploitation evidence
Disclosed: evidence found.
CVE published 1 Dec 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.
What to do
AI-suggested
Organizations should immediately implement strict input validation and output encoding on all user-supplied data in the affected parameters (hname, hemail, hpassword, hphone, hcity) within updateprofile.php and hprofile.php. Employ context-aware encoding (e.g., HTML entity encoding) to neutralize injected scripts. Deploy a Web Application Firewall (WAF) configured to detect and block XSS payloads targeting these endpoints. Conduct thorough code reviews and security testing to identify and remediate similar vulnerabilities in other components. Restrict access to the affected pages to trusted users and monitor logs for suspicious activity indicative of attempted XSS exploitation. Educate users about phishing risks stemming from XSS attacks. Plan for an urgent update or replacement of the BBMS software with a secure version once available. Ensure compliance with GDPR by promptly reporting any data breaches resulting from exploitation.
Description
A cross-site scripting (XSS) vulnerability exists in the Blood Bank Management System 1.0 within the updateprofile.php and hprofile.php components. The application fails to properly sanitize or encode user-supplied input before rendering it in response. An attacker can inject malicious JavaScript payloads into the hname, hemail, hpassword, hphone, hcity parameters, which are then executed in the victim's browser when the page is viewed.