vulnerability / NVI-00007413 / Revision 3
CodeIgniter4 has a validation bypass when uploading file extensions via `ext_in` rule
OSV carries this publisher advisory for codeigniter4/framework. This is an aggregated source copy; consult the original publisher and compare update dates.
This report has not inspected your inventory, configuration, deployed build, reachability or evidence. A catalog listing and a severity score do not establish exposure or compromise.
01 / Meaning
Why it matters
Published affected context helps an owner decide what evidence to gather. This report has not examined your application.
9.8 CRITICAL (3.1)
security-advisories@github.com severity; no combined Null risk score.
0.775%
FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.5579. Missing scores are unknown.
As of · FIRST EPSS
02 / Applicability
The affected context
Affected versions, configuration prerequisites and known exclusions are public. Confirm each one against the deployed service.
codeigniter4/framework
source listedECOSYSTEM: introduced 0; fixed 4.7.3
### Impact The `ext_in` upload validation rule checked the MIME-derived guessed extension instead of the client-provided filename extension. As a result, an uploaded file named `shell.php` containing GIF-like content could pass validation such as: ``` uploaded[avatar]|is_image[avatar]|mime_in[avatar,image/gif]|ext_in[avatar,gif] ``` because the detected MIME type maps to `gif`, even though the uploaded filename extension is `php`. Applications are impacted if they: - accept user-controlled uploads, - rely on `ext_in` to validate the uploaded filename extension, - save uploaded files using the original client filename: `$file->move($path)`, - store uploads in a web-accessible directory, - and allow PHP or other executable files to run from that directory. In those conditions, this may lead to arbitrary code execution. The default application does not expose such an upload endpoint. ### Patches Upgrade to v4.7.3 or later. ### Workarounds - Save uploads outside the public web root, preferably under `writable/uploads` - Use `$file->store()` or `$file->move($path, $file->getRandomName())` instead of preserving the original filename - Disable script execution in any public upload dir
03 / Response
What to do next
- vendor patch
The original advisory lists fixed boundaries 4.7.3 for codeigniter4/framework. Confirm the publisher’s latest guidance.
Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. GitHub Advisory Database via OSV
- investigate
Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.
Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. FIRST EPSS
A fixed release is not deployment evidence.
Check current vendor support and compatibility. After making a change, verify the deployed build and relevant runtime conditions. Keep the evidence, owner and time. An updated lockfile alone does not prove what is running.
04 / Limits
What this report cannot establish
- Customer inventory, deployment, reachability and exploitation have not been inspected.
- NVD lastModified does not establish freshness of every associated CPE record.
05 / Provenance
Sources you can inspect
Each assertion retains its source. Mirrored records may repeat one underlying publisher; additional links are not independent corroboration.
- GHSA-2gr4-ppc7-7mhx ↗
GitHub Advisory Database via OSV · vendor advisory
Observed . GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.
- CVE-2026-48062 ↗
NIST National Vulnerability Database · official catalog
Observed . This product uses data from the NVD API but is not endorsed or certified by the NVD.
- CVE-2026-48062 ↗
FIRST EPSS · official catalog
Observed . FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.
Public revision history
Only published revisions appear here. Routine fetches do not create a material-change event.
- Revision 3 ·
Source facts changed; compare the preserved prior revision.
- Revision 2 ·
Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.
- Revision 1 ·
First indexed by Null; source disclosure date is shown separately.