Overview
In this blog post, we will delve into the details of a critical vulnerability identified as CVE-2025-52921. This vulnerability was discovered in Innoshop, a popular e-commerce software platform. The vulnerability affects versions up to and including 0.4.1, and if exploited, it could lead to potential system compromise or data leakage. This vulnerability is particularly concerning due to its severity and the potential impact on businesses using Innoshop for their e-commerce operations. The severity of this issue is underlined by its CVSS Severity Score of 9.9, which indicates a critical risk.
Vulnerability Summary
CVE ID: CVE-2025-52921
Severity: Critical (9.9 CVSS Score)
Attack Vector: Network
Privileges Required: High (Authenticated User)
User Interaction: Required
Impact: Potential system compromise or data leakage
Affected Products
Escape the Surveillance Era
Most apps won’t tell you the truth.
They’re part of the problem.
Phone numbers. Emails. Profiles. Logs.
It’s all fuel for surveillance.
Ameeba Chat gives you a way out.
- • No phone number
- • No email
- • No personal info
- • Anonymous aliases
- • End-to-end encrypted
Chat without a trace.
Product | Affected Versions
Innoshop | Up to and including 0.4.1
How the Exploit Works
An authenticated attacker can exploit this vulnerability by manipulating the File Manager functions in the admin panel. Initially, the attacker would upload a crafted file. The application checks if the uploaded files are image files; however, this check can be bypassed by simply renaming the uploaded file to have a .php extension using the Rename Function.
This bypass is possible due to the application only relying on frontend checks to restrict the administrator from changing the extension of uploaded files to .php. This restriction can be easily bypassed using any proxy tool, such as BurpSuite. Once the attacker renames the file and gives it the .php extension, a GET request can be used to trigger the execution of code on the server.
Conceptual Example Code
Below is a conceptual example of how the vulnerability might be exploited. This represents the HTTP request made to rename the uploaded file to a .php extension.
GET /admin/file_manager/rename?old_filename=attack.jpg&new_filename=attack.php HTTP/1.1
Host: target.example.com
Authorization: Bearer [User's Authenticated JWT]Now, with the file renamed to a .php extension, the attacker can trigger the execution of the code on the server with the following GET request:
GET /uploads/attack.php HTTP/1.1
Host: target.example.comPlease note that the above is only a conceptual representation and the actual exploit may vary based on the specific environment and conditions.
Mitigation Guidance
To mitigate the threat from this vulnerability, it is advised to apply the vendor patch as soon as it becomes available. In the meantime, using a Web Application Firewall (WAF) or Intrusion Detection System (IDS) can serve as a temporary mitigation measure.