CodeIgniter: Uploaded file extension validation bypass in is_image and mime_in rules
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| codeigniter4 | CodeIgniter4 | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Codeigniter | Codeigniter |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-mmj4-63m4-r6h5 | CodeIgniter: Uploaded file extension validation bypass in `is_image` and `mime_in` rules |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.800% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Codeigniter
Codeigniter codeigniter |
|
| Vendors & Products |
Codeigniter
Codeigniter codeigniter |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | CodeIgniter is a PHP full-stack web framework. Prior to 4.7.4, the is_image and mime_in upload validation rules do not independently enforce a safe client filename extension, allowing a remote attacker to upload executable content when an application preserves the client filename and stores uploads in a web-accessible script-enabled directory. Applications are impacted when they validate uploads using is_image or mime_in without an independent safe extension check (such as ext_in on patched versions), save uploaded files using the client-supplied filename, and place uploads in a web-accessible directory where PHP files can execute. This issue is fixed in version 4.7.4. | |
| Title | CodeIgniter: Uploaded file extension validation bypass in is_image and mime_in rules | |
| Weaknesses | CWE-434 | |
| References |
| |
| Metrics |
cvssV3_1
|