CVE-2025-59747
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' parameter in '/clt/resetPassword.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 the 'l' parameter of /clt/resetPassword.asp in AndSoft e-TMS v25.03. An attacker can inject malicious JavaScript code into the URL that executes in victim's browsers when they access the crafted link.
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 your system for AndSoft e-TMS software. Look for web server directories containing the application files, typically in web root folders or application-specific directories.Affected if AndSoft e-TMS is not present on the system, the vulnerability does not apply.
-
Verify the exact version numberLocate version information for the AndSoft e-TMS installation. Check application metadata, About pages, or configuration files that display the software version.Affected if The installed version is exactly 25.03 - other versions are not affected by this specific CVE.
-
Confirm the vulnerable endpoint existsCheck if the file /clt/resetPassword.asp exists in the web application directory. This is the specific endpoint mentioned in the CVE.Affected if The file does not exist, the vulnerability cannot be exploited.
-
Test for the vulnerable parameterExamine the resetPassword.asp page to confirm it accepts a parameter named 'l'. Review the page source or test by submitting the form with the 'l' parameter.Affected if The 'l' parameter is not used by the page, the XSS vulnerability does not apply.
-
Verify the parameter reflects user inputSubmit a benign test value in the 'l' parameter (such as a simple text string) and observe if it reflects back in the HTML response without proper encoding.Affected if User input in the 'l' parameter is reflected in the response without sanitization, indicating the XSS vulnerability is present.
The system is affected only if AndSoft e-TMS version 25.03 is installed AND the /clt/resetPassword.asp endpoint exists AND the 'l' parameter reflects user input without sanitization.
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 for the 'l' parameter in the password reset endpoint. Use context-appropriate output encoding to neutralize special characters before reflecting user input in the HTML response.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-59747 — 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-59747 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