CVE-2024-12641
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 · uneditedTenderDocTransfer from Chunghwa Telecom has a Reflected Cross-site scripting vulnerability. The application sets up a simple local web server and provides APIs for communication with the target website. Due to the lack of CSRF protection for the APIs, unauthenticated remote attackers could use specific APIs through phishing to execute arbitrary JavaScript code in the user’s browser. Since the web server set by the application supports Node.Js features, attackers can further leverage this to run OS commands.
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 confidenceTenderDocTransfer from Chunghwa Telecom sets up a local web server providing APIs for target website communication. The application lacks CSRF protection on these APIs, allowing unauthenticated remote attackers through phishing to inject and execute arbitrary JavaScript code in victim's browsers. Since the application's web server supports Node.js features, attackers can further exploit this to execute OS commands on the victim machine.
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>= 0.41.151, < 0.41.157CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
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.
-
Verify TenderDocTransfer installationLocate the TenderDocTransfer application on the system and identify its version number through the application's about page, version info in the installation directory, or by running the application binary with a version flagAffected if The installed version is >= 0.41.151 and < 0.41.157
-
Confirm the local web server is runningCheck if the TenderDocTransfer web server process is active, typically listening on localhost ports. Use commands like netstat or ps to identify running web server processes associated with TenderDocTransferAffected if The web server is running and accessible, exposing the vulnerable API endpoints
-
Check for Node.js integrationExamine the TenderDocTransfer configuration or documentation to determine if Node.js features are enabled for the web server, as this is required for the XSS-to-command-execution escalationAffected if Node.js features are enabled in the web server configuration
The environment is affected if TenderDocTransfer version is 0.41.151 through 0.41.156 inclusive, the local web server is active, and Node.js features are enabled on the web server.
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.
dbcve · scoped0.41.157
Implement CSRF protection (e.g., anti-CSRF tokens) on all API endpoints, apply strict input validation and output encoding to prevent XSS, and restrict or sandbox the Node.js capabilities exposed through the web server to prevent OS command execution.
0.41.157 or later
- Identify the currently installed version of TenderDocTransfer
- Upgrade TenderDocTransfer to version 0.41.157 or later
- Verify the upgrade was successful by checking the version number
- Test the application to confirm the XSS vulnerability is remediated
- Ensure the web server is properly configured with appropriate access controls
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-12641 — 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-2024-12641 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