CVE-2025-57145: n/a
A cross-site scripting (XSS) vulnerability exists in the search-autootaxi.php endpoint of the ATSMS web application. The application fails to properly sanitize user input submitted through a form field, allowing an attacker to inject arbitrary JavaScript code. The malicious payload is stored in the backend and executed when a user or administrator accesses the affected report page. This allows attackers to exfiltrate session cookies, hijack user sessions, and perform unauthorized actions in the context of the victims browser.
AI Analysis
Technical Summary
CVE-2025-57145 is a cross-site scripting (XSS) vulnerability identified in the ATSMS web application, specifically within the search-autootaxi.php endpoint. This vulnerability arises because the application does not properly sanitize user input submitted through a form field. As a result, an attacker can inject arbitrary JavaScript code that is stored persistently in the backend. When a user or administrator accesses the affected report page, the malicious script executes in their browser context. This persistent XSS attack vector enables attackers to exfiltrate sensitive information such as session cookies, hijack user sessions, and perform unauthorized actions on behalf of the victim within the application. The vulnerability is particularly dangerous because it leverages stored payloads, increasing the likelihood of exploitation by multiple users, including privileged administrators. Although no specific affected versions or patches have been disclosed, the vulnerability is publicly known as of September 16, 2025, and no known exploits are currently reported in the wild. The lack of a CVSS score requires an independent severity assessment based on the potential impact and exploitability factors.
Potential Impact
For European organizations using the ATSMS web application, this vulnerability poses significant risks. The ability to execute arbitrary JavaScript in the context of authenticated users can lead to session hijacking, unauthorized data access, and manipulation of application functionality. This could compromise the confidentiality and integrity of sensitive data managed by ATSMS, potentially including personal data protected under GDPR. The persistent nature of the XSS increases the attack surface, as multiple users may be exposed to the malicious payload. Organizations operating critical transportation or taxi management services that rely on ATSMS could face operational disruptions, reputational damage, and regulatory penalties if exploited. Furthermore, attackers could leverage this vulnerability as a foothold for broader network intrusion or lateral movement within an organization’s infrastructure.
Mitigation Recommendations
To mitigate this vulnerability, organizations should implement strict input validation and output encoding on all user-supplied data, especially within the search-autootaxi.php endpoint. Employing a robust web application firewall (WAF) configured to detect and block XSS payloads can provide an additional layer of defense. Regularly auditing and sanitizing stored data to remove malicious scripts is recommended. Since no patches are currently available, organizations should consider restricting access to the vulnerable endpoint to trusted users only and monitor logs for suspicious activity. Implementing Content Security Policy (CSP) headers can help limit the impact of injected scripts by restricting the sources from which scripts can be loaded. Finally, educating users and administrators about the risks of XSS and encouraging cautious behavior when interacting with reports can reduce exploitation likelihood.
Affected Countries
Germany, France, United Kingdom, Italy, Spain, Netherlands, Belgium, Poland, Sweden, Austria
CVE-2025-57145: n/a
Description
A cross-site scripting (XSS) vulnerability exists in the search-autootaxi.php endpoint of the ATSMS web application. The application fails to properly sanitize user input submitted through a form field, allowing an attacker to inject arbitrary JavaScript code. The malicious payload is stored in the backend and executed when a user or administrator accesses the affected report page. This allows attackers to exfiltrate session cookies, hijack user sessions, and perform unauthorized actions in the context of the victims browser.
AI-Powered Analysis
Technical Analysis
CVE-2025-57145 is a cross-site scripting (XSS) vulnerability identified in the ATSMS web application, specifically within the search-autootaxi.php endpoint. This vulnerability arises because the application does not properly sanitize user input submitted through a form field. As a result, an attacker can inject arbitrary JavaScript code that is stored persistently in the backend. When a user or administrator accesses the affected report page, the malicious script executes in their browser context. This persistent XSS attack vector enables attackers to exfiltrate sensitive information such as session cookies, hijack user sessions, and perform unauthorized actions on behalf of the victim within the application. The vulnerability is particularly dangerous because it leverages stored payloads, increasing the likelihood of exploitation by multiple users, including privileged administrators. Although no specific affected versions or patches have been disclosed, the vulnerability is publicly known as of September 16, 2025, and no known exploits are currently reported in the wild. The lack of a CVSS score requires an independent severity assessment based on the potential impact and exploitability factors.
Potential Impact
For European organizations using the ATSMS web application, this vulnerability poses significant risks. The ability to execute arbitrary JavaScript in the context of authenticated users can lead to session hijacking, unauthorized data access, and manipulation of application functionality. This could compromise the confidentiality and integrity of sensitive data managed by ATSMS, potentially including personal data protected under GDPR. The persistent nature of the XSS increases the attack surface, as multiple users may be exposed to the malicious payload. Organizations operating critical transportation or taxi management services that rely on ATSMS could face operational disruptions, reputational damage, and regulatory penalties if exploited. Furthermore, attackers could leverage this vulnerability as a foothold for broader network intrusion or lateral movement within an organization’s infrastructure.
Mitigation Recommendations
To mitigate this vulnerability, organizations should implement strict input validation and output encoding on all user-supplied data, especially within the search-autootaxi.php endpoint. Employing a robust web application firewall (WAF) configured to detect and block XSS payloads can provide an additional layer of defense. Regularly auditing and sanitizing stored data to remove malicious scripts is recommended. Since no patches are currently available, organizations should consider restricting access to the vulnerable endpoint to trusted users only and monitor logs for suspicious activity. Implementing Content Security Policy (CSP) headers can help limit the impact of injected scripts by restricting the sources from which scripts can be loaded. Finally, educating users and administrators about the risks of XSS and encouraging cautious behavior when interacting with reports can reduce exploitation likelihood.
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
 - 5.1
 - Assigner Short Name
 - mitre
 - Date Reserved
 - 2025-08-17T00:00:00.000Z
 - Cvss Version
 - null
 - State
 - PUBLISHED
 
Threat ID: 68c97dc81745d1bd2332d286
Added to database: 9/16/2025, 3:10:00 PM
Last enriched: 9/16/2025, 3:10:24 PM
Last updated: 11/4/2025, 8:18:46 AM
Views: 38
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2025-20749: CWE-121 Stack Overflow in MediaTek, Inc. MT6789, MT6835, MT6855, MT6878, MT6879, MT6886, MT6897, MT6899, MT6983, MT6985, MT6989, MT6991, MT8169, MT8188, MT8195, MT8196, MT8781, MT8796
UnknownCVE-2025-20748: CWE-120 Classic Buffer Overflow in MediaTek, Inc. MT6890, MT7615, MT7622, MT7663, MT7915, MT7916, MT7981, MT7986
UnknownCVE-2025-20747: CWE-121 Stack Overflow in MediaTek, Inc. MT2718, MT2737, MT6835, MT6878, MT6886, MT6897, MT6899, MT6982, MT6985, MT6986, MT6986D, MT6989, MT6990, MT6991, MT8676, MT8678, MT8755, MT8893
UnknownCVE-2025-20746: CWE-121 Stack Overflow in MediaTek, Inc. MT2718, MT2737, MT6835, MT6878, MT6886, MT6897, MT6899, MT6982, MT6985, MT6986, MT6986D, MT6989, MT6990, MT6991, MT8676, MT8678, MT8755, MT8893
UnknownCVE-2025-20745: CWE-416 Use After Free in MediaTek, Inc. MT2718, MT6989, MT6991, MT8370, MT8390, MT8395, MT8676, MT8678, MT87920
UnknownActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.