CVE-2025-59739
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 · uneditedOperating 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_original.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 confidenceAndSoft e-TMS v25.03 contains an OS command injection vulnerability in the login form at /clt/LOGINFRM_original.ASP. The 'm' parameter in POST requests is not properly sanitized, allowing attackers to inject and execute arbitrary operating system commands on the server.
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= 25.03CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm AndSoft e-TMS is installedCheck for the presence of the e-TMS application on the server. Look for directories or IIS/Apache configurations referencing 'e-TMS' or 'AndSoft'. Check running services or installed programs for e-TMS.Affected if AndSoft e-TMS software is found on the system
-
Verify the installed version is 25.03Locate version information for the e-TMS installation. Check application logs, configuration files, or the application banner/footer on web pages. Compare your version against the affected range (25.03).Affected if The installed version is exactly 25.03
-
Confirm the vulnerable endpoint existsTest for the presence of /clt/LOGINFRM_original.ASP on the web server. This is the login form path where the command injection vulnerability exists.Affected if The endpoint /clt/LOGINFRM_original.ASP returns a valid HTTP response (200 or similar)
-
Inspect the login form for the 'm' parameterSubmit a request to /clt/LOGINFRM_original.ASP and examine the login form's HTML. Look for an input field named 'm' in the POST request. The vulnerability exists when this parameter accepts user input without sanitization.Affected if The login form contains a parameter named 'm' that accepts user input in POST requests
A user is affected if AndSoft e-TMS version 25.03 is installed and the /clt/LOGINFRM_original.ASP login form with the 'm' parameter is accessible.
Generated from the published advisory. Verify against your own configuration.
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 dataImmediately restrict network access to the e-TMS application while the vulnerability is addressed. The fix requires implementing strict input validation and sanitization on the 'm' parameter to prevent command injection, followed by comprehensive testing to verify the remediation.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-59739 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-59739 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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