dbcve.org
E TmsApplication · Andsoft

CVE-2025-59743

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
SQL injection vulnerability in AndSoft's e-TMS v25.03. This vulnerability could allow an attacker to retrieve, create, update, and delete databases by sending a POST request. The relationship between parameter and assigned identifier is a 'SessionID' cookie in '/inc/connect/CONNECTION.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

SQL injection vulnerability in AndSoft's e-TMS v25.03 allows unauthenticated attackers to inject arbitrary SQL commands via the SessionID cookie parameter on the /inc/connect/CONNECTION.ASP endpoint. This critical flaw enables full database compromise including data exfiltration and manipulation.

MitigationImplement parameterized queries (prepared statements) for the SessionID cookie parameter in CONNECTION.ASP and add proper input validation. Until a vendor patch is available, consider deploying a WAF to filter malicious SQL injection payloads.

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. Identify AndSoft e-TMS installation
    Check for AndSoft e-TMS web application presence by inspecting web server directories or scanning for the application's login page or known file paths such as /inc/connect/ or searching for 'e-TMS' or 'AndSoft' in HTTP responses or server configuration.
    Affected if The AndSoft e-TMS software is found running on the server.
  2. Verify software version is 25.03
    Locate version information by checking application files, login page source, error pages, or administrative interfaces for build or version number indicators. Compare against the affected version 25.03.
    Affected if The installed version is exactly 25.03.
  3. Confirm vulnerable endpoint exists
    Test for the presence of /inc/connect/CONNECTION.ASP by sending a request to this path and observing the response. Check if the file exists on the web server.
    Affected if The endpoint /inc/connect/CONNECTION.ASP is accessible and returns a response.
  4. Check if POST requests to vulnerable path are accepted
    Send a POST request to /inc/connect/CONNECTION.ASP with a test payload and observe whether the application processes the request. Verify the server accepts cookies in POST requests to this endpoint.
    Affected if The application accepts POST requests to this endpoint and processes the SessionID cookie parameter.
  5. Review cookie handling configuration
    Inspect application configuration files or web server logs for SessionID cookie processing related to the CONNECTION.ASP endpoint. Look for how cookies are parsed and used in database queries.
    Affected if The application processes SessionID cookies in the context of database connections without parameterized query handling.

A system is affected if AndSoft e-TMS version 25.03 is installed and the /inc/connect/CONNECTION.ASP endpoint is accessible, accepting POST requests with a SessionID cookie that gets incorporated into SQL queries.

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 parameterized queries (prepared statements) for the SessionID cookie parameter in CONNECTION.ASP and add proper input validation. Until a vendor patch is available, consider deploying a WAF to filter malicious SQL injection payloads.

Fix this in E Tms Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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