CVE-2025-59738
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_BET.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 confidenceA critical OS command injection vulnerability exists in AndSoft e-TMS v25.03. The 'm' parameter in the login form endpoint '/clt/LOGINFRM_BET.ASP' accepts user input that is improperly sanitized and passed directly to operating system command execution, allowing unauthenticated attackers to execute arbitrary system commands via crafted POST requests.
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 installationInspect your web server for the presence of the AndSoft e-TMS application. Look for directories or application files containing 'etms', 'e-tms', or 'andsoft' in the web root. Check the HTTP response headers or application footer for product identification.Affected if AndSoft e-TMS is installed on the server and responds to requests.
-
Identify the exact version numberLocate version information for the installed AndSoft e-TMS. Check the application's about page, footer, configuration files, or HTTP headers for a version string. Compare it against the affected version 25.03.Affected if The installed version is exactly 25.03.
-
Verify vulnerable endpoint existsSend a GET request to /clt/LOGINFRM_BET.ASP or access it via browser. Confirm the login form endpoint exists and returns a valid response.Affected if The /clt/LOGINFRM_BET.ASP endpoint is accessible and returns a login form.
-
Check for 'm' parameter in login formInspect the HTML source of the /clt/LOGINFRM_BET.ASP page. Look for a form input parameter named 'm' that accepts user input.Affected if The login form contains an input parameter named 'm' that can accept user-supplied values.
You are affected if AndSoft e-TMS version 25.03 is installed and the /clt/LOGINFRM_BET.ASP endpoint 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 dataImplement strict input validation and sanitization on all parameters, particularly the 'm' parameter; replace any unsafe system command calls with parameterized APIs or secure libraries; apply vendor patch if available; deploy a WAF as a temporary compensating control.
- Consultation6.0 h
- Implementation16.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 $9,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-59738 — 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-59738 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