Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-48062 – Unrestricted File Upload leading to RCE – CodeIgniter4 prior to 4.7.3

Be the first to know when new zero-days emerge:

Summary

CVE-2026-48062 is a critical unrestricted file upload vulnerability (CWE-434) in the CodeIgniter4 PHP web framework affecting all versions prior to 4.7.3. The flaw resides in the ext_in upload validation rule, which incorrectly inspects the MIME-derived file extension rather than the client-supplied filename extension, allowing an attacker to bypass file type restrictions and upload a server-executable file that can lead to Remote Code Execution (RCE). The vulnerability carries a CVSS v3.1 base score of 9.8 (Critical) with no authentication or user interaction required.

Technical details

  • Root cause: The ext_in rule in system/Validation/StrictRules/FileRules.php evaluates the extension inferred from the file’s detected MIME type rather than the extension present in the client-supplied filename. A file named shell.php that contains GIF-like magic bytes is detected as image/gif, causing its MIME-derived extension to evaluate as gif—not php—so validation rules such as ext_in[avatar,gif] and mime_in[avatar,image/gif] pass without error.
  • Trigger conditions: An application is exploitable when it (1) accepts user-controlled file uploads, (2) relies on ext_in to gate allowed file types, (3) preserves the original client filename by saving via $file->move($path), (4) stores uploads in a web-accessible directory, and (5) permits PHP (or other script) execution from that directory. These conditions are common in real-world features such as avatar or profile image uploads.
  • Attack vector: An unauthenticated network attacker submits a crafted multipart file upload request containing a PHP web shell disguised with GIF magic bytes; the framework validates and stores it under its original .php filename in a publicly reachable path.
  • Impact: Once saved, the attacker retrieves the file via HTTP to execute arbitrary PHP code on the server, resulting in full RCE—leading to complete confidentiality, integrity, and availability compromise of the underlying system.

Affected software

  • CodeIgniter4 (package codeigniter4/framework) — all versions prior to 4.7.3

Severity

  • CVSS v3.1 Base Score: 9.8 (Critical)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate – Patch: Upgrade CodeIgniter4 to version 4.7.3 or later, which corrects the ext_in rule to validate against the client-supplied filename extension.
  • If immediate patching is not feasible:
    • Store uploaded files outside the web root so they cannot be directly requested over HTTP.
    • Rename uploaded files to a server-generated random name using $file->getRandomName() rather than preserving the original client filename.
    • Disable PHP (and other script interpreter) execution in upload directories via web server configuration (e.g., php_flag engine off in .htaccess or equivalent Nginx directives).
    • Supplement ext_in validation by explicitly checking $file->getClientExtension() against an allowlist in application-level logic.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge