/

CVE-2026-64838

Severity:

HIGH RISK

(8.3)

Path Traversal (CWE-22) in ICEcoder File Operations

CVE-2026-64838

Deferred

Vulnerability type

Category:

Path Traversal

CWE:

CWE-22

Impact:

Unauthorized File Disclosure and File Manipulation

Severity:

HIGH RISK

(8.3)

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

ICEcoder through version 8.1 does not properly validate the oldFileName parameter used during file move and rename operations. An authenticated user may exploit path traversal to move files writable by the PHP process into the web-accessible project directory, exposing their contents and removing the originals.

Affected context

The vulnerability occurs in ICEcoder file move and rename functionality when the application accepts an oldFileName value without sufficiently restricting it to the intended document root. Risk is higher when the PHP process can write to files outside the project directory and the destination is served directly by the web server.

Exploit preconditions

  • Attack surface: Authenticated ICEcoder file move or rename functionality
  • Required access: A valid account with permission to perform file operations
  • Trigger point: Processing of the oldFileName parameter
  • Why exploitation is possible: Path traversal input can cause the application to resolve a source file outside the permitted document root, provided that file is writable by the PHP process

Why this happens

The underlying bug is insufficient canonicalization and boundary validation of a user-controlled filesystem path. The application uses the supplied source filename in a file operation without reliably confirming that the resolved path remains within the authorized document root. This behavior maps to CWE-22: Improper Limitation of a Pathname to a Restricted Directory, commonly known as path traversal.

Potential impact

  • Sensitive file contents could be disclosed through the web-accessible project directory
  • Files writable by the PHP process could be relocated or deleted
  • Application configuration or source files may be exposed
  • Website integrity could be affected through unauthorized file manipulation
  • Subsequent compromise could occur if exposed or modified files contain security-sensitive data

General mitigation guidance

Mitigation generally focuses on enforcing a strict filesystem trust boundary for every move and rename operation.

Common defensive patterns include:

  • Canonicalizing source and destination paths before authorization checks
  • Rejecting any resolved path that falls outside the configured document root
  • Avoiding security decisions based only on string prefix or raw path comparisons
  • Applying allowlisted file-operation roots and secure-by-default path APIs
  • Reducing PHP process write permissions and separating writable data from web-accessible content
  • Preventing direct web access to sensitive files through server policy

How teams detect issues like this

Organizations can look for this weakness through:

  • Static analysis rules for user-controlled values passed to filesystem move, rename, or delete functions
  • Code review checks requiring canonicalization and containment validation before file operations
  • Tests using normalized, encoded, and platform-specific path forms to verify directory boundaries
  • Runtime monitoring for authenticated file operations involving paths outside approved roots
  • Policy enforcement that separates application write locations from web-served directories

Automated security review tools may help identify path construction and insufficient validation patterns.

Sources

SourceLink
github.comgithub.com/Caycon/cve-advisories/blob/main/2026/ICEcoder/CVE-2026-64838.md
github.comgithub.com/icecoder/ICEcoder
github.comgithub.com/icecoder/ICEcoder/blob/4a61847ef7bb0360735cf1d55c45e5de9746e24e/lib/file-control.php#L198
vulncheck.comvulncheck.com/advisories/icecoder-through-8.1-path-traversal-via-oldfilename-parameter

Frequently asked

questions

It may be exploitable through the ICEcoder web interface when the attacker has authenticated access and the application can reach writable files outside the document root.

Exploitation requires an account permitted to use the affected file move or rename functionality. The PHP process must also have suitable filesystem permissions.

Resolve and canonicalize both source and destination paths, then enforce that they remain within an explicitly allowlisted directory before performing the operation.

Use dedicated path-handling APIs, apply least-privilege filesystem permissions, keep sensitive files outside web-accessible locations, and include traversal-focused tests and code-review checks.

Find out what's already
exploitable in your codebase.