CVE-2025-4075 in VMSMan
Summary
by MITRE • 04/29/2025
A vulnerability was found in VMSMan up to 20250416. It has been rated as problematic. Affected by this issue is some unknown functionality of the file /login.php. The manipulation of the argument Email with the input ">alert(1) leads to cross site scripting. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Analysis
by VulDB Data Team • 06/08/2026
This vulnerability resides within VMSMan version 20250416 and represents a critical cross-site scripting flaw located in the login.php file. The issue manifests when an attacker manipulates the Email parameter through a malicious input string containing ">alert(1) which demonstrates a classic reflected cross-site scripting vulnerability. The vulnerability affects the authentication mechanism and allows attackers to inject malicious javascript code that executes in the context of a victim's browser session. This particular weakness falls under CWE-79 which specifically addresses cross-site scripting vulnerabilities where untrusted data is directly incorporated into web pages without proper validation or encoding.
The attack vector is entirely remote, meaning an attacker can exploit this vulnerability without requiring physical access to the system or local network presence. The exploit is publicly available and has been disclosed, removing any barrier to exploitation. This makes the vulnerability particularly dangerous as it can be leveraged by any malicious actor with knowledge of the target system's URL structure. The reflected nature of the vulnerability means that the malicious payload is embedded in a URL or form submission and then reflected back to the user's browser, executing the javascript code in the victim's context.
The operational impact of this vulnerability extends beyond simple script execution. A successful XSS attack could enable attackers to hijack user sessions, steal sensitive authentication tokens, perform unauthorized actions on behalf of users, or redirect victims to malicious websites. The vulnerability particularly threatens user authentication workflows since it targets the login functionality where users enter sensitive information. This creates a potential pathway for credential theft and unauthorized access to the system. The lack of vendor response to early disclosure attempts indicates a potential delay in patch development or remediation efforts, leaving users exposed to active exploitation.
Mitigation strategies should include immediate implementation of input validation and output encoding for all user-supplied data, particularly within authentication forms. The system should employ proper content security policies to prevent execution of unauthorized scripts. Additionally, implementing proper sanitization of the Email parameter in login.php would prevent the injection of malicious javascript code. Organizations should consider deploying web application firewalls to detect and block suspicious input patterns. The vulnerability demonstrates the critical importance of secure coding practices and timely patch management as outlined in the mitre attack framework where such vulnerabilities often serve as initial access vectors for more sophisticated attacks. Regular security assessments and code reviews should be conducted to identify similar issues in other application components and maintain overall system security posture.