CVE-2025-59761
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 · uneditedCross-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, demo, demo2, TNTLOGIN, UO and SuppConn' parameters in '/clt/LOGINFRM_DLG.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 confidenceReflected XSS in AndSoft e-TMS v25.03 allows execution of arbitrary JavaScript in victim's browser via malicious URLs containing payloads in the 'l', 'demo', 'demo2', 'TNTLOGIN', 'UO', or 'SuppConn' parameters on the /clt/LOGINFRM_DLG.ASP login form endpoint.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm AndSoft e-TMS versionLocate the installed version of AndSoft e-TMS in your system inventory, software documentation, or by accessing the application admin panel or about page. Check any version information displayed in the application footer or system information screens.Affected if The installed version is exactly 25.03 (version 25.03)
-
Verify vulnerable endpoint existsAttempt to access the URL path /clt/LOGINFRM_DLG.ASP on your web server (e.g., https://yourserver/clt/LOGINFRM_DLG.ASP). Use a browser or curl command to check if the endpoint responds.Affected if The endpoint /clt/LOGINFRM_DLG.ASP returns a valid HTTP response (200 OK) and displays a login form
-
Test parameter reflection for XSSSend a crafted GET request to the vulnerable endpoint with a test payload in one of the suspected parameters. For example: /clt/LOGINFRM_DLG.ASP?l=<script>alert(1)</script> . Then inspect the HTTP response body to see if the <script> tag or payload is reflected as-is without encoding.Affected if The test payload (or any JavaScript tags) appears in the response body unencoded or unsanitized, indicating the parameter is vulnerable to XSS
-
Test all vulnerable parametersRepeat the XSS reflection test for each of these parameters: l, demo, demo2, TNTLOGIN, UO, and SuppConn. Send each parameter separately with a benign XSS test string and examine whether the value is reflected in the response without proper encoding.Affected if Any of these six parameters reflect user-supplied input without HTML encoding or sanitization
You are affected if you are running AndSoft e-TMS version 25.03 and the /clt/LOGINFRM_DLG.ASP endpoint reflects unencoded input from any of the l, demo, demo2, TNTLOGIN, UO, or SuppConn parameters in its response.
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 input validation and output encoding on all user-supplied parameters at the LOGINFRM_DLG.ASP endpoint, particularly the identified vulnerable parameters, to prevent script injection.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-59761 — 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-59761 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