dbcve.org
E TmsApplication · Andsoft

CVE-2025-59735

CRITICAL · 9.8 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 →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
Operating system command injection vulnerability in AndSoft's e-TMS v25.03. This vulnerability allows an attacker to execute operating system commands on the server by sending a POST request. The relationship between parameter and assigned identifier is a 'm' parameter in '/clt/LOGINFRM.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

OS command injection vulnerability in AndSoft e-TMS v25.03 where the 'm' parameter in POST requests to /clt/LOGINFRM.ASP is not properly sanitized, allowing attackers to inject and execute arbitrary operating system commands on the server.

MitigationImplement strict input validation and sanitization on all user-supplied parameters, particularly the 'm' parameter. Use parameterized queries or safe API calls instead of passing user input to system shell commands. Apply principle of least privilege to the application service account.

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Verify AndSoft e-TMS installation and version
    Locate the AndSoft e-TMS application installation directory and check the version information (typically in an about page, version file, or application header). Confirm the installed version is exactly 25.03.
    Affected if The installed version of AndSoft e-TMS is 25.03
  2. Confirm the vulnerable endpoint exists
    Check if the web application exposes the /clt/LOGINFRM.ASP endpoint. This is typically found in the web root directory under the 'clt' folder.
    Affected if The /clt/LOGINFRM.ASP file exists and is accessible via the web server
  3. Check if POST parameter 'm' is processed
    Review the LOGINFRM.ASP source code or web application configuration to confirm the 'm' parameter is accepted in POST requests and passed to system execution functions without sanitization.
    Affected if The application accepts the 'm' parameter in POST requests and passes it to shell execution functions (such as shell, exec, system, or similar) without input validation
  4. Inspect web server access logs for exploitation attempts
    Review web server logs (IIS, Apache, or native logs) for POST requests to /clt/LOGINFRM.ASP containing suspicious commands in the 'm' parameter (look for shell metacharacters like &, |, ;, $, or command keywords).
    Affected if Log entries show POST requests to LOGINFRM.ASP with encoded or plain OS commands in the 'm' parameter
  5. Verify the application runs with elevated privileges
    Check the service account or application pool identity under which e-TMS executes. Determine if it has privileges beyond what the application requires.
    Affected if The e-TMS application runs with administrative or high-privilege account permissions

You are affected if AndSoft e-TMS version 25.03 is installed and the /clt/LOGINFRM.ASP endpoint processes the 'm' parameter 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 strict input validation and sanitization on all user-supplied parameters, particularly the 'm' parameter. Use parameterized queries or safe API calls instead of passing user input to system shell commands. Apply principle of least privilege to the application service account.

Fix this in E Tms Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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