CVE-2025-59765
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_LF.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 confidenceReflected cross-site scripting (XSS) vulnerability in AndSoft e-TMS v25.03 affecting the login form at /clt/LOGINFRM_LF.ASP. Multiple parameters (l, demo, demo2, TNTLOGIN, UO, SuppConn) do not properly sanitize user input, allowing injection of malicious JavaScript code that executes in victim browsers when they click a crafted URL.
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 the system inventory, about page, or application header/footer and verify it is exactly version 25.03Affected if Version is 25.03
-
Verify vulnerable endpoint existsAttempt to access the URL path /clt/LOGINFRM_LF.ASP on the web server (e.g., https://target/clt/LOGINFRM_LF.ASP) and confirm the login form loadsAffected if The endpoint responds and displays the login form
-
Test parameter reflection for XSSSend HTTP requests to the login form with malicious payloads in each affected parameter (l, demo, demo2, TNTLOGIN, UO, SuppConn), for example: /clt/LOGINFRM_LF.ASP?l=<script>alert(1)</script> and inspect the HTTP response body to see if the payload is reflected unencodedAffected if Any of the affected parameters reflect the raw input without HTML encoding (e.g., <script> tags appear literally in the response)
-
Inspect response headers and encodingCapture the HTTP response from the login form and check the Content-Type header; verify that response does not include proper XSS protection headers like Content-Security-PolicyAffected if Response lacks proper encoding or security headers and reflects user input unescaped
A user is affected if they are running AndSoft e-TMS version 25.03 and the login form at /clt/LOGINFRM_LF.ASP reflects any of the parameters l, demo, demo2, TNTLOGIN, UO, or SuppConn without HTML encoding in the HTTP 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 proper input validation and output encoding (e.g., Server.HTMLEncode in ASP classic) for all user-supplied parameters before reflecting them in the HTTP response.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-59765 — 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-59765 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