CVE-2025-59758
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_CYLOG.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 vulnerability in AndSoft e-TMS v25.03 login form (/clt/LOGINFRM_CYLOG.ASP). The parameters 'l', 'demo', 'demo2', 'TNTLOGIN', 'UO', and 'SuppConn' do not properly sanitize user input, allowing injection of malicious JavaScript via crafted URLs.
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.
-
Identify AndSoft e-TMS installationCheck if the web application 'AndSoft e-TMS' or 'e-TMS' is running in your environment by reviewing web server content, application directories, or scanning for the product name in HTTP headers or page footers.Affected if AndSoft e-TMS is present in your environment
-
Verify the software versionLocate the version information for the e-TMS installation, typically found in application configuration files, about pages, or in the HTTP headers. Common paths include the application root or admin panels.Affected if The installed version is exactly 25.03
-
Confirm the affected endpoint existsAttempt to access or check for the presence of /clt/LOGINFRM_CYLOG.ASP on your web server. This is the login form endpoint where the vulnerability resides.Affected if The endpoint /clt/LOGINFRM_CYLOG.ASP is accessible on your server
-
Identify vulnerable parameter exposureReview your web application logs or use a browser to test the affected parameters (l, demo, demo2, TNTLOGIN, UO, SuppConn) by submitting crafted requests to the login form endpoint. Look for unescaped or unsanitized reflection of these parameter values in the response.Affected if Any of the parameters l, demo, demo2, TNTLOGIN, UO, or SuppConn are reflected in the HTML response without proper encoding
You are affected if you are running AndSoft e-TMS version 25.03 and the login form endpoint /clt/LOGINFRM_CYLOG.ASP is accessible with vulnerable parameter handling.
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 context-aware output encoding for all identified parameters at the affected endpoint, and validate/sanitize input according to expected data types.
- 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-59758 — 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-59758 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