CVE-2025-59746
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 'm' parameter in '/lib/asp/alert.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 allows attackers to inject malicious JavaScript via the 'm' parameter in /lib/asp/alert.asp. When a victim clicks a crafted URL, the unsanitized parameter value is reflected back in the response, executing in the victim's browser context.
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 installationLocate the application by checking web server directories for 'AndSoft' or 'e-TMS' folders, or query the web server for typical e-TMS paths such as /lib/asp/, /TMS/, or root paths serving .asp files. Identify the version by reviewing version files, login pages, or HTTP headers if the application displays version information.Affected if The installed application is AndSoft e-TMS version 25.03
-
Verify alert.asp endpoint existsRequest the path /lib/asp/alert.asp on the web server using a GET request. For example: curl -s http://TARGET/lib/asp/alert.asp or visit the URL in a browser.Affected if The endpoint returns a valid HTTP response (200 or similar) rather than a 404, indicating the file exists and is accessible
-
Confirm parameter handling of 'm'Send a test request with a benign value in the 'm' parameter, such as: /lib/asp/alert.asp?m=testvalue. Inspect the HTTP response body to see if the value 'testvalue' appears unchanged or unescaped in the HTML output.Affected if The 'm' parameter value is reflected directly in the response without HTML encoding or sanitization
-
Review access logs for exploitation attemptsExamine web server access logs (IIS, Apache, or other) for requests to /lib/asp/alert.asp with suspicious 'm' parameter values containing HTML tags, script elements, or JavaScript event handlers. Search for patterns like <script, javascript:, onerror=, onload= in the query string.Affected if Logs contain requests with malicious payloads in the 'm' parameter, indicating potential exploitation
The environment is affected if AndSoft e-TMS version 25.03 is running and the /lib/asp/alert.asp endpoint is accessible, as the 'm' 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 'm' parameter in alert.asp. Use context-appropriate escaping when reflecting user input into HTML/JavaScript responses.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-59746 — 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-59746 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