CVE-2025-63528

8.5

Blood Bank Management System · Blood Bank Management System

A cross-site scripting (XSS) vulnerability in Blood Bank Management System 1.0 allows attackers to execute malicious scripts via the error parameter in blooddinfo.php.

Executive summary

A stored cross-site scripting vulnerability in the Blood Bank Management System 1.0 poses a high risk to authenticated users by allowing arbitrary JavaScript execution.

Vulnerability

This is a cross-site scripting (XSS) vulnerability located in the blooddinfo.php component, where the application fails to sanitize user-supplied input in the error parameter. The CVSS vector (PR:L) indicates that an authenticated user is required to trigger the payload.

Business impact

Successful exploitation allows an attacker to execute arbitrary JavaScript in the context of an authenticated user session. Given the CVSS score of 8.5, this vulnerability could lead to session hijacking, unauthorized actions performed on behalf of the user, or the exfiltration of sensitive information, potentially resulting in significant data compromise and loss of system integrity.

Remediation

Immediate Action: Since a specific patch is currently unknown, administrators should restrict access to the blooddinfo.php component and ensure that all user input is strictly validated and encoded before being rendered.

Proactive Monitoring: Monitor web server access logs for anomalous requests containing script tags or suspicious encoded characters directed at the blooddinfo.php endpoint.

Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to detect and block common XSS payloads targeting URL parameters, which can provide effective virtual patching until an official update is released.

Exploitation status

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

Analyst recommendation

Given the high CVSS score and the presence of a public proof-of-concept, this vulnerability warrants immediate attention. Organizations should prioritize isolating the affected component and implementing input validation controls to prevent script injection while awaiting a vendor-supplied security update.

Sources