CVE-2025-59773

6.1 MEDIUM

📋 TL;DR

This reflected cross-site scripting (XSS) vulnerability in AndSoft's e-TMS v25.03 allows attackers to inject malicious JavaScript via specially crafted URLs targeting specific parameters. When victims click these malicious links, the attacker can execute arbitrary code in their browser session, potentially stealing credentials or performing actions on their behalf. Organizations using the vulnerable version of this transportation management system are affected.

💻 Affected Systems

Products:
  • AndSoft e-TMS
Versions: v25.03
Operating Systems: Windows (ASP-based application)
Default Config Vulnerable: ⚠️ Yes
Notes: The vulnerability affects the '/clt/LOGINFRM_TP.ASP' endpoint with specific parameters: l, demo, demo2, TNTLOGIN, UO, and SuppConn.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could steal administrator credentials, hijack user sessions, deface the application, or redirect users to malicious sites, potentially leading to complete system compromise.

🟠

Likely Case

Attackers will typically use this to steal session cookies and credentials, enabling unauthorized access to the transportation management system and sensitive data.

🟢

If Mitigated

With proper input validation and output encoding, the malicious scripts would be neutralized, preventing execution while maintaining normal application functionality.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: LIKELY
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

Reflected XSS vulnerabilities are commonly exploited and require minimal technical skill to weaponize into phishing campaigns.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: https://www.incibe.es/en/incibe-cert/notices/aviso/update-24092025-multiple-vulnerabilities-andsofts-e-tms

Restart Required: No

Instructions:

1. Contact AndSoft vendor for patch availability. 2. Apply any available security updates. 3. Test the fix in a non-production environment first.

🔧 Temporary Workarounds

Web Application Firewall (WAF) Rules

all

Implement WAF rules to block malicious XSS payloads targeting the vulnerable parameters.

Input Validation Filter

windows

Add server-side input validation to sanitize the vulnerable parameters before processing.

🧯 If You Can't Patch

  • Implement strict Content Security Policy (CSP) headers to restrict script execution
  • Deploy the application behind a reverse proxy with XSS filtering capabilities

🔍 How to Verify

Check if Vulnerable:

Test the '/clt/LOGINFRM_TP.ASP' endpoint with XSS payloads in the vulnerable parameters (l, demo, demo2, TNTLOGIN, UO, SuppConn) and check if scripts execute.

Check Version:

Check application version in administrative interface or configuration files

Verify Fix Applied:

Retest with the same XSS payloads after applying fixes; scripts should be properly encoded or blocked from execution.

📡 Detection & Monitoring

Log Indicators:

  • Unusual parameter values containing script tags or JavaScript in access logs
  • Multiple failed login attempts from suspicious sources

Network Indicators:

  • HTTP requests with encoded script payloads in URL parameters
  • Traffic patterns showing users being redirected to malicious sites

SIEM Query:

source="web_server" AND (url="*LOGINFRM_TP.ASP*" AND (param="*<script>*" OR param="*javascript:*" OR param="*onerror=*"))

🔗 References

📤 Share & Export