CVE-2024-51225 in Vehicle Record Management System
Summary
by MITRE • 03/23/2026
A stored cross-site scripting (XSS) vulnerability in the component /admin/add-brand.php of Phpgurukul Vehicle Record Management System v1.0 allows attackers to execute arbitrary web scripts or HTML via injecting a crafted payload into the brandname parameter.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Analysis
by VulDB Data Team • 03/27/2026
The vulnerability identified as CVE-2024-51225 represents a critical stored cross-site scripting flaw within the Phpgurukul Vehicle Record Management System version 1.0. This security weakness specifically affects the administrative component located at /admin/add-brand.php, where user input is not properly sanitized or validated before being stored and subsequently rendered in web pages. The vulnerability arises from insufficient input validation mechanisms that fail to adequately filter malicious payloads injected through the brandname parameter, creating an environment where attackers can persistently inject malicious code that executes in the context of other users' browsers.
The technical implementation of this vulnerability stems from the application's failure to employ proper output encoding and input sanitization techniques when processing user-supplied data. When administrators or legitimate users view brand information stored in the database, the malicious script code embedded within the brandname parameter executes automatically in their browsers, potentially leading to session hijacking, credential theft, or redirection to malicious websites. This stored nature of the vulnerability means that once the malicious payload is injected, it remains persistent and affects all users who access the affected page without requiring repeated exploitation attempts. The flaw aligns with CWE-79 which specifically addresses cross-site scripting vulnerabilities, and represents a clear violation of secure coding practices that should prevent untrusted data from being directly rendered in web contexts.
The operational impact of this vulnerability extends beyond simple script execution, as it provides attackers with a persistent foothold within the administrative interface of the vehicle management system. Successful exploitation could enable unauthorized individuals to manipulate brand information, potentially leading to more severe consequences such as data corruption, unauthorized access to sensitive vehicle records, or even complete system compromise if additional vulnerabilities exist within the application's architecture. The attack vector is particularly concerning because it targets the administrative add-brand functionality, suggesting that attackers could modify core system data and potentially gain elevated privileges. This vulnerability also maps to several ATT&CK techniques including T1566 for initial access through malicious input and T1059 for command and scripting interpreter execution, making it a significant threat to the overall security posture of organizations relying on this system.
Mitigation strategies for CVE-2024-51225 should focus on immediate input validation and output encoding implementations. Organizations must ensure that all user-supplied data, particularly within administrative interfaces, undergoes strict sanitization before being stored in the database and rendered in web pages. This includes implementing proper HTML entity encoding for all output, employing Content Security Policy headers to limit script execution, and conducting thorough input validation using allowlists rather than denylists. Additionally, regular security audits and penetration testing should be conducted to identify similar vulnerabilities within the application's codebase, while comprehensive user input sanitization should be implemented across all components that accept user data. The system should also implement proper access controls and monitoring to detect unauthorized modifications to brand information, and organizations should consider implementing web application firewalls to provide additional layers of protection against similar attacks.