CVE-2025-63533

8.5

Blood Bank Management System · Blood Bank Management System

A cross-site scripting (XSS) vulnerability in Blood Bank Management System 1.0 allows authenticated users to execute malicious JavaScript via unsanitized input in profile update parameters.

Executive summary

An authenticated cross-site scripting vulnerability in the Blood Bank Management System 1.0 poses a high risk of session hijacking and unauthorized administrative actions.

Vulnerability

This is a stored cross-site scripting (XSS) vulnerability located in the updateprofile.php and rprofile.php components. An authenticated attacker can inject malicious payloads into the rname, remail, rpassword, rphone, or rcity parameters, which execute when a victim views the affected profile page.

Business impact

The vulnerability carries a CVSS score of 8.5, indicating a high level of severity. Successful exploitation allows an attacker to execute scripts in the context of a victim's session, potentially leading to unauthorized data access, account takeover, or the manipulation of sensitive medical records within the management system.

Remediation

Immediate Action: Since no official patch is currently available, administrators should restrict access to the application to trusted personnel only and implement strict input validation on the server side.

Proactive Monitoring: Review web application access logs for unusual request patterns targeting updateprofile.php or rprofile.php and monitor for anomalous script execution behaviors.

Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to detect and block common XSS payloads in HTTP POST requests sent to the vulnerable parameters.

Exploitation status

Public Exploit Available: Yes, a public proof-of-concept exists as documented in the provided GitHub research repository.

Analyst recommendation

Given the high CVSS score and the existence of a public proof-of-concept, this vulnerability presents a significant risk to the integrity of the Blood Bank Management System. Organizations should prioritize the implementation of WAF-based filtering and strict access controls until the vendor releases a secure version that properly sanitizes user input.

Sources