dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-7452

MEDIUM · 6.3 CVSS v3.1 Published 2025-07-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable 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
A vulnerability was found in kone-net go-chat up to f9e58d0afa9bbdb31faf25e7739da330692c4c63. It has been declared as critical. This vulnerability affects the function GetFile of the file go-chat/api/v1/file_controller.go of the component Endpoint. The manipulation of the argument fileName leads to path traversal. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. This product is using a rolling release to provide continious delivery. Therefore, no version details for affected nor updated releases are available.

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 confidence

Path traversal vulnerability in the GetFile function of go-chat/api/v1/file_controller.go allows remote attackers to manipulate the fileName argument and access files outside the intended directory through directory traversal sequences (e.g., ../../).

MitigationImplement strict input validation using canonical path resolution with directory boundary checks, or use a whitelist approach to ensure requested files are strictly within the allowed document root directory.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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 go-chat installation
    Locate the go-chat application binary or source code. Check for the presence of the file_controller.go file in the api/v1/ directory.
    Affected if The file api/v1/file_controller.go exists and contains a GetFile function handling user-supplied fileName parameters.
  2. Determine installed version
    Run 'go-chat --version' or check the application binary metadata/version information. If built from source, check git tags or version files.
    Affected if The installed version is unpatched and falls within any vulnerable version range for CVE-2025-7452.
  3. Verify file endpoint accessibility
    Check if the file download/upload API endpoint is exposed. Review application routing configuration for routes handling /file or /api/v1/file/* paths.
    Affected if The GetFile endpoint is publicly or internally accessible without additional authentication layers.
  4. Inspect GetFile function for path validation
    Examine the source code of go-chat/api/v1/file_controller.go. Look for path traversal protection such as filepath.Clean, filepath.Join with base directory checks, or whitelist validation before file operations.
    Affected if The GetFile function lacks proper canonical path resolution and does not verify that the resolved path remains within an allowed directory boundary.
  5. Test for traversal vulnerability
    If permitted by policy, send a request to the file endpoint with a fileName parameter containing ../../etc/passwd or similar traversal sequences and observe the response.
    Affected if The application returns files outside the intended document root directory or exhibits unexpected file access behavior.

The environment is affected if go-chat with a vulnerable GetFile function is running, the file endpoint is accessible, and no path traversal protection is implemented in the code.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation using canonical path resolution with directory boundary checks, or use a whitelist approach to ensure requested files are strictly within the allowed document root directory.

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-7452 — 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-7452 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