CVE-2025-13282
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 developed by Chunghwa Telecom has a Arbitrary File Delete 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, allowing attackers to delete arbitrary files on the user's system.
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 confidenceTenderDocTransfer is a local web server application by Chunghwa Telecom that provides APIs for communicating with target websites. The application lacks CSRF protection on its APIs, and one API contains an Absolute Path Traversal vulnerability, allowing unauthenticated remote attackers via phishing to delete arbitrary files on the user's system.
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.159CVSS 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
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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.
-
Locate TenderDocTransfer installationCheck common installation directories such as C:\Program Files\TenderDocTransfer, C:\TenderDocTransfer, or the application's installation path. Also check for running processes named TenderDocTransfer or related service names.Affected if The application is found installed on the system
-
Identify installed versionCheck the version by examining the executable file properties (right-click on the main .exe file and view Details/Version), or check the application's About/Version page if accessible via http://localhost:[port] where the application typically runs.Affected if The version is lower than 0.41.159
-
Verify web server is runningCheck if the TenderDocTransfer local web server is active by attempting to access localhost on common ports (typically 8080, 8000, or the configured port). Use command: netstat -an | findstr LISTENING to list active listening ports.Affected if The web server is listening and accessible
-
Check for path traversal indicators in logsExamine application logs (typically in a /logs or /data/logs folder within the installation directory) for suspicious requests containing path traversal patterns such as ../../ or absolute Windows paths like C:\ in DELETE requests.Affected if Logs show DELETE requests with path traversal patterns to locations outside the expected application directory
-
Inspect for unauthorized file deletionsReview file system access logs, Windows Event Viewer Security logs, or the application's own activity logs for evidence of file deletions in unexpected directories (outside the intended document transfer folder).Affected if File deletion events occurred in directories not configured as the application's working directory
A system is affected if TenderDocTransfer version is below 0.41.159 and the local web server is running and accessible, making it possible for remote attackers to exploit the path traversal vulnerability via phishing.
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.159
Users should avoid using the application until a vendor patch is available. Implement network segmentation to limit exposure. Monitor for suspicious deletion activity. Consider disabling the application temporarily if possible.
0.41.159 or later
- 1. Download the latest version of TenderDocTransfer (version 0.41.159 or later) from the official vendor source
- 2. Backup all existing TenderDocTransfer configuration files and data
- 3. Stop the TenderDocTransfer service if currently running
- 4. Install the new version (0.41.159 or later) following the vendor's installation instructions
- 5. Verify the installation was successful by checking the application version
- 6. Restart the TenderDocTransfer service
- 7. Test that the application functions normally with the new version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation16.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 $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-13282 — 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-13282 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