Out-of-directory file write via unsanitized upload filename
Published Jul 31, 2026 · Updated Jul 31, 2026
Path traversal in CodeIgniter 4 before 4.7.4 allows remote attackers to write uploaded content outside the intended directory. UploadedFile::move() uses getName() as the destination name without sanitize_filename() when its optional name argument is omitted. Reachability requires an application upload path that calls this default form, and destination permissions and server configuration bound the resulting file write.
Summary
What happened
Path traversal in CodeIgniter 4 before 4.7.4 allows remote attackers to write uploaded content outside the intended directory. UploadedFile::move() uses getName() as the destination name without sanitize_filename() when its optional name argument is omitted. Reachability requires an application upload path that calls this default form, and destination permissions and server configuration bound the resulting file write.
The record
- CVE
- CVE-2026-63222
- Published
- Jul 31, 2026
- Updated
- Jul 31, 2026
- Vendor
- CodeIgniter Foundation
- Product
- CodeIgniter 4
- Classifications
- CWE-22, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 31, 2026CVE publishedPublication date reported by the CVE source.
- Jul 31, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 4.7.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo