dbcve.org
E TmsApplication · Andsoft

CVE-2025-59772

MEDIUM · 6.1 CVSS v3.1 Published 2025-10-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Cross-site scripting (XSS) vulnerability reflected in AndSoft's e-TMS v25.03. This vulnerability allows an attacker to execute JavaScript code in the victim's browser by sending them a malicious URL. The relationship between parameter and assigned identifier is 'l, demo, demo2, TNTLOGIN, UO and SuppConn' parameters in '/clt/LOGINFRM_SIL.ASP'.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A reflected Cross-Site Scripting (XSS) vulnerability in AndSoft e-TMS v25.03 allows attackers to inject malicious JavaScript code through multiple parameters (l, demo, demo2, TNTLOGIN, UO, SuppConn) in the /clt/LOGINFRM_SIL.ASP login page. When victims click a crafted URL, the unsanitized parameter values are reflected back in the response, enabling script execution in their browser context.

MitigationImplement context-aware output encoding and input validation for all user-controllable parameters on the login form. Alternatively, deploy a Web Application Firewall (WAF) as a temporary mitigation to block XSS payloads in URL parameters.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
E TmsApplication
Affected:= 25.03

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm AndSoft e-TMS is installed
    Identify if the AndSoft e-TMS web application is running in your environment. Look for web server responses, application directories, or service banners referencing 'AndSoft' or 'e-TMS'. Check your web server logs or application inventory for this product.
    Affected if AndSoft e-TMS is present in your environment
  2. Verify the product version
    Determine the installed version of AndSoft e-TMS. Check application configuration files, the login page source, version disclosure in HTTP headers, or consult your software asset management records. The affected version is specifically 25.03.
    Affected if The installed version is exactly 25.03
  3. Check if the login form endpoint exists
    Attempt to access the URL path /clt/LOGINFRM_SIL.ASP on your web server. This is the login page where the XSS vulnerability exists. A 200 OK response confirms the endpoint is present.
    Affected if The /clt/LOGINFRM_SIL.ASP login page is accessible and returns successfully
  4. Test parameter reflection without sanitization
    Send a crafted request to /clt/LOGINFRM_SIL.ASP with a test payload in one of the affected parameters (l, demo, demo2, TNTLOGIN, UO, or SuppConn). For example: /clt/LOGINFRM_SIL.ASP?l=<script>alert(1)</script>. Inspect the HTTP response body to see if the parameter value is reflected verbatim without encoding or sanitization.
    Affected if The parameter value is reflected in the response without HTML encoding or sanitization

You are affected if AndSoft e-TMS version 25.03 is running and the login page at /clt/LOGINFRM_SIL.ASP reflects user-supplied parameter values without sanitization.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement context-aware output encoding and input validation for all user-controllable parameters on the login form. Alternatively, deploy a Web Application Firewall (WAF) as a temporary mitigation to block XSS payloads in URL parameters.

Fix this in E Tms Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-59772 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-59772 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data