dbcve.org
TenderdoctransferApplication · Cht

CVE-2025-13283

HIGH · 7.1 CVSS v3.1 Published 2025-11-17
Fix available
A fix is available. Upgrade to 0.41.159 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges

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 · unedited
TenderDocTransfer developed by Chunghwa Telecom has a Arbitrary File Copy and Paste 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 in the APIs, unauthenticated remote attackers could use these APIs through phishing. Additionally, one of the APIs contains an Absolute Path Traversal vulnerability. Attackers can copy arbitrary files on the user's system and paste them into any path, which poses a potential risk of information leakage or could consume hard drive space by copying files in large volumes.

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 confidence

TenderDocTransfer by Chunghwa Telecom is a local web server application providing APIs for document transfer. The application lacks CSRF protection on its APIs, allowing unauthenticated remote attackers to invoke APIs through phishing. Additionally, one API contains an Absolute Path Traversal vulnerability that enables attackers to copy arbitrary files from the user's system to any destination path, leading to information disclosure or denial-of-service via disk space exhaustion.

MitigationImplement CSRF token validation and SameSite cookie policies on all APIs, and fix the path traversal vulnerability by validating and sanitizing file paths to prevent absolute path access and restrict copy operations to allowed directories.

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
TenderdoctransferApplication
Affected:< 0.41.159

CVSS 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
Unchanged
Confidentiality
High
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if TenderDocTransfer is installed
    Check for running processes or installed files related to TenderDocTransfer or 'cht Tenderdoctransfer'. Look for process names, service entries, or installation directories on the system.
    Affected if TenderDocTransfer is found running or installed on the system
  2. Determine the installed version
    Locate the application version information (check application binaries, config files, or the web interface version display if available) and compare it to the affected range of versions before 0.41.159.
    Affected if The installed version is lower than 0.41.159
  3. Verify the web API is accessible
    Check if the TenderDocTransfer web server is listening on its expected port (commonly ports 80, 443, or a custom port). Attempt to access the API endpoints from the local system or network.
    Affected if The web API is accessible (even locally), enabling the CSRF and path traversal attacks to be exploited
  4. Confirm path traversal API exposure
    Identify which API endpoint handles file copy or transfer operations. Test whether the API accepts absolute file paths in its parameters (e.g., copy source/destination parameters).
    Affected if The file copy/transfer API accepts absolute paths as input without validation

A system is affected if TenderDocTransfer is installed with a version lower than 0.41.159 and its web API is accessible, allowing the CSRF attack surface and path traversal vulnerability to be exploited.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 0.41.159 or later
Fixed in 0.41.159
Interim mitigation

Implement CSRF token validation and SameSite cookie policies on all APIs, and fix the path traversal vulnerability by validating and sanitizing file paths to prevent absolute path access and restrict copy operations to allowed directories.

Recommended fix Moderate confidence

0.41.159 or later

  1. Identify the current installed version of TenderDocTransfer
  2. Upgrade TenderDocTransfer to version 0.41.159 or later to resolve the Absolute Path Traversal vulnerability
  3. After upgrading, verify that the local web server APIs now include proper CSRF protection
  4. Restrict access to the local web server to trusted networks or localhost only as an additional defense-in-depth measure

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Tenderdoctransfer Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,180
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-13283 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-13283 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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