/

CVE-2026-75328

Severity:

HIGH RISK

(7.5)

Path Traversal (CWE-22) in DocSys Java DocController

CVE-2026-75328

Deferred

Vulnerability type

Category:

Path Traversal

CWE:

CWE-22

Impact:

Arbitrary File Read and Sensitive Information Disclosure

Severity:

HIGH RISK

(7.5)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A path traversal vulnerability in DocSys-master's downloadDocEx interface may allow an attacker to read files outside the intended document directory.

The issue becomes risky when user-controlled path information reaches the file-download operation without sufficient canonicalization and containment checks.

Affected context

The vulnerability occurs in the downloadDocEx interface within src/com/DocSystem/controller/DocController.java. It may affect deployments where a request can influence the file or document path used by the download handler and where the application does not reliably constrain resolved paths to an approved storage location.

Exploit preconditions

  • Attack surface: The document-download interface exposed by the application
  • Required access: Access to submit requests to the affected interface; authentication requirements depend on deployment configuration
  • Trigger point: Processing a download request containing attacker-influenced path information
  • Why exploitation is possible: Insufficient path normalization or boundary validation may allow a requested path to resolve outside the intended document directory

Why this happens

The underlying bug is improper limitation of a pathname to a designated directory. When application input is incorporated into filesystem operations without robust canonicalization and directory-boundary verification, traversal elements or equivalent path representations may redirect the operation to unintended locations.

This behavior maps to CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal').

Potential impact

  • An attacker may read application configuration files
  • Sensitive credentials, tokens, or private documents could be disclosed
  • Internal source code or operational data may be exposed
  • Information obtained from files could support further compromise

General mitigation guidance

Mitigation generally focuses on reducing trust in request-derived paths and ensuring file access remains within an explicitly permitted storage boundary.

Common defensive patterns include:

  • Resolving requested paths against a fixed base directory and verifying the canonical result remains inside that directory
  • Preferencing opaque document identifiers or server-side mappings over client-supplied filesystem paths
  • Applying strict allowlists for document names, extensions, and storage locations
  • Rejecting encoded, alternate, or platform-specific path representations that do not match the expected format
  • Running the application with the least filesystem privileges necessary
  • Keeping sensitive configuration and credential files outside web-accessible storage locations

How teams detect issues like this

Organizations can identify path traversal risks through:

  • Static analysis rules for filesystem APIs receiving request parameters
  • Code review checks for missing canonicalization and directory-boundary validation
  • Tests that compare resolved paths against approved storage roots using varied path representations
  • Runtime monitoring for unusual download requests, repeated path normalization failures, or access attempts outside document directories
  • Application policies that require opaque identifiers and centralized file-access helpers

Sources

SourceLink
github.comgithub.com/fangtang7/CVE/blob/main/DocSys/DocSys%E4%BB%BB%E6%84%8F%E6%96%87%E4%BB%B6%E8%AF%BB%E5%8F%96.md

Frequently asked

questions

It may be remotely exploitable when the downloadDocEx interface is reachable and request data can influence the selected file path.

Authentication requirements depend on the application's access controls. Any account or role permitted to invoke the download interface may be relevant if path restrictions are insufficient.

Use server-side document identifiers, resolve files only beneath a fixed approved directory, and verify the canonical path before opening the file.

Centralize file-access logic, avoid exposing filesystem paths to clients, apply least-privilege permissions, and include traversal-focused testing and static analysis in development workflows.

Find out what's already
exploitable in your codebase.