dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-29865

HIGH · 8.7 CVSS v4.0 Published 2025-08-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
96/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in TAGFREE X-Free Uploader XFU allows Path Traversal.This issue affects X-Free Uploader: from 1.0.1.0084 before 1.0.1.0085, from 2.0.1.0034 before 2.0.1.0035.

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

Path traversal vulnerability in TAGFREE X-Free Uploader XFU allows attackers to write files outside the intended restricted directory through manipulation of file path parameters during upload. The vulnerability affects versions 1.0.1.0084 and 2.0.1.0034 and is patched in versions 1.0.1.0085 and 2.0.1.0035.

MitigationUpgrade to X-Free Uploader version 1.0.1.0085 or 2.0.1.0035 or later. If immediate upgrade is not possible, implement strict input validation to reject path traversal sequences (..) and validate that uploaded files remain within intended directories.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 TAGFREE X-Free Uploader XFU is present
    Review application components, dependencies, or installed modules for XFU or X-Free Uploader. Check web application source code or deployment manifests for references to 'XFU', 'X-Free Uploader', or 'TAGFREE'.
    Affected if X-Free Uploader component is found in the environment
  2. Determine the installed XFU version
    Locate version information in application metadata, configuration files, or the XFU component itself. Compare against the affected versions 1.0.1.0084 and 2.0.1.0034.
    Affected if Installed version matches 1.0.1.0084 or 2.0.1.0034 exactly
  3. Verify the file upload feature is enabled
    Check if the XFU upload module is active and accessible. Review application configuration to confirm upload functionality is not disabled or restricted.
    Affected if Upload functionality is enabled and accessible to users or processes
  4. Confirm the application handles file path parameters
    Examine upload handling code or configuration to verify the application accepts file path parameters that could be manipulated for path traversal.
    Affected if The application accepts user-controllable path parameters during file upload operations

The environment is affected if X-Free Uploader XFU is present with version 1.0.1.0084 or 2.0.1.0034 and the upload feature with path parameter handling is enabled.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to X-Free Uploader version 1.0.1.0085 or 2.0.1.0035 or later. If immediate upgrade is not possible, implement strict input validation to reject path traversal sequences (..) and validate that uploaded files remain within intended directories.

Recommended fix High confidence

Upgrade to X-Free Uploader version 1.0.1.0085 (for 1.x branch) or 2.0.1.0035 (for 2.x branch)

  1. 1. Identify your current X-Free Uploader version by checking the application or system documentation
  2. 2. If running version 1.0.1.0084, upgrade to version 1.0.1.0085
  3. 3. If running version 2.0.1.0034, upgrade to version 2.0.1.0035
  4. 4. Download the updated version from the official vendor or trusted distribution channel
  5. 5. Apply the upgrade following the vendor's standard upgrade procedure
  6. 6. Verify the new version is correctly installed and the service is operational

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-29865 — 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-29865 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