CVE-2025-52921

9.9 CRITICAL

📋 TL;DR

This vulnerability allows authenticated attackers to achieve remote code execution on Innoshop servers by bypassing file upload restrictions. Attackers can upload a malicious file, rename it to have a .php extension using the admin panel's File Manager, and then execute arbitrary code. This affects all Innoshop installations up to version 0.4.1 with admin panel access.

💻 Affected Systems

Products:
  • Innoshop
Versions: through 0.4.1
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: Requires authenticated access to the admin panel. Default installations with admin credentials exposed are particularly vulnerable.

⚠️ Manual Verification Required

This CVE does not have specific version information in our database, so automatic vulnerability detection cannot determine if your system is affected.

Why? The CVE database entry doesn't specify which versions are vulnerable (no version ranges provided by the vendor/NVD).

🔒 Custom verification scripts are available for registered users. Sign up free to download automated test scripts.

Recommended Actions:
  1. Review the CVE details at NVD
  2. Check vendor security advisories for your specific version
  3. Test if the vulnerability is exploitable in your environment
  4. Consider updating to the latest version as a precaution

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete server compromise allowing attackers to execute arbitrary code, steal sensitive data, install backdoors, pivot to other systems, and potentially take full control of the hosting environment.

🟠

Likely Case

Attackers gain shell access to the server, allowing them to exfiltrate database contents, modify website files, install cryptocurrency miners, or use the server as a pivot point for further attacks.

🟢

If Mitigated

With proper network segmentation and least privilege access, impact could be limited to the web application directory, though sensitive data exposure would still occur.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: LIKELY
Unauthenticated Exploit: ✅ No
Complexity: LOW

Exploitation requires admin credentials but is straightforward using proxy tools like BurpSuite to bypass frontend validation.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: Unknown

Restart Required: No

Instructions:

Check the official GitHub repository for updates. If a patch is available, update to the latest version. Review and apply any security advisories from the vendor.

🔧 Temporary Workarounds

Disable File Manager Rename Function

all

Remove or disable the rename functionality in the admin panel's File Manager to prevent attackers from changing file extensions.

Modify the File Manager component to remove rename functionality or restrict it to non-executable file types

Implement Server-Side File Validation

all

Add server-side validation that checks file extensions and MIME types before allowing uploads or renames.

Implement server-side validation in upload and rename handlers to reject .php and other executable extensions

🧯 If You Can't Patch

  • Restrict admin panel access to trusted IP addresses only using firewall rules or web server configuration
  • Implement web application firewall (WAF) rules to block requests attempting to rename files to .php extensions

🔍 How to Verify

Check if Vulnerable:

Check if your Innoshop version is 0.4.1 or earlier. Test if you can upload a file and rename it to .php extension using proxy tool interception.

Check Version:

Check the Innoshop version in the admin panel or review the application's version file

Verify Fix Applied:

Attempt to reproduce the exploit after applying fixes. Verify that server-side validation prevents renaming files to .php extensions.

📡 Detection & Monitoring

Log Indicators:

  • File rename operations changing extensions to .php
  • Uploads of non-image files followed by rename operations
  • Admin panel login attempts from unusual locations

Network Indicators:

  • HTTP POST requests to file rename endpoints with .php extensions
  • Traffic patterns showing file upload followed by immediate rename

SIEM Query:

source="web_logs" AND (uri="/admin/file-manager/rename" AND request_body LIKE "%.php%") OR (uri="/admin/file-manager/upload" AND user_agent NOT LIKE "%browser%")

🔗 References

📤 Share & Export