dbcve.org
E TmsApplication · Andsoft

CVE-2025-59748

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' and 'reset' parameters in '/clt/changepassword.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 · moderate confidence

Reflected XSS vulnerability in AndSoft e-TMS v25.03 allows injection of malicious JavaScript through the 'l' and 'reset' parameters in the /clt/changepassword.asp endpoint. Attackers can craft URLs that, when clicked by victims, execute arbitrary JavaScript in their browsers due to improper input sanitization.

MitigationImplement proper input validation and output encoding for all user-supplied parameters in the changepassword.asp page, specifically the 'l' and 'reset' parameters, before reflecting them in HTML output.

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 installation
    Locate the application by checking for the presence of the /clt/ directory path in web server logs or by identifying the e-TMS web application banner. Check web server configuration files for the e-TMS application path.
    Affected if AndSoft e-TMS is not installed or the /clt/ path does not exist in the web root.
  2. Identify e-TMS version
    Check the application's about page, footer, or version information within the web interface. Alternatively, review any version.txt, version.info, or configuration files within the e-TMS web directory that may disclose the software version.
    Affected if The installed version is exactly 25.03.
  3. Verify changepassword.asp endpoint exists
    Access the URL path /clt/changepassword.asp in a web browser or using curl to confirm the endpoint is reachable and part of the installed application.
    Affected if The endpoint returns a 404 error or is not found.
  4. Test 'l' parameter for reflected input
    Navigate to /clt/changepassword.asp?l=teststring and inspect the HTML response page source to see if 'teststring' appears anywhere in the output without encoding or sanitization.
    Affected if The input value from the 'l' parameter is reflected verbatim in the HTML response without proper encoding.
  5. Test 'reset' parameter for reflected input
    Navigate to /clt/changepassword.asp?reset=teststring and inspect the HTML response page source to see if 'teststring' appears anywhere in the output without encoding or sanitization.
    Affected if The input value from the 'reset' parameter is reflected verbatim in the HTML response without proper encoding.

A user is affected if AndSoft e-TMS version 25.03 is installed and the /clt/changepassword.asp endpoint reflects unsanitized input from the 'l' or 'reset' parameters back into the HTML output.

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 proper input validation and output encoding for all user-supplied parameters in the changepassword.asp page, specifically the 'l' and 'reset' parameters, before reflecting them in HTML output.

Fix this in E Tms Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-59748 — 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-59748 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