Innoshop bis einschließlich 0.4.1 erlaubt Directory Traversal über FileManager API Endpunkte. Ein authentifizierter Angreifer mit Zugriff auf das Admin Panel könnte dies missbrauchen, um: (1) die Dateisystemstruktur vollständig abzubilden vi

This Directory Traversal vulnerability grants an authenticated attacker extensive control over the InnoShop server's file system. By manipulating the basefolder parameter in the /api/filemanager/files endpoint, an attacker can enumerate the entire file system structure. Further exploitation allows the creation of arbitrary directories, the copying of files to readable locations, and the deletion of existing files. This could lead to the exposure of sensitive data, including configuration files, database credentials, and potentially even source code. The ability to delete files poses a significant risk of data loss and service disruption.

Organizations using InnoShop for e-commerce or online store management are at risk, particularly those running versions 0 through 0.4.1. Shared hosting environments where multiple users share the same server instance are also at increased risk, as a compromised admin account on one store could potentially be used to exploit this vulnerability on other stores.

• php: Examine web server access logs for requests to /api/filemanager endpoints containing ../ sequences in the basefolder or other parameters.

grep 'api/file_manager.*\/\/\/' /var/log/apache2/access.log

• php: Check for unusual file creations or deletions within the InnoShop application directory.

find /var/www/innoshop -type f -ctime -1

• generic web: Monitor for unexpected file reads or modifications within the InnoShop application directory. • generic web: Review the application's configuration files for any insecure file paths or permissions.

1. 2025-06-23Disclosure

   disclosure

1. Reserviert2025-06-21
2. Veröffentlicht2025-06-23
3. EPSS aktualisiert2026-03-23

The primary mitigation for CVE-2025-52922 is to upgrade InnoShop to version 0.4.2 or later, which contains the fix. If upgrading immediately is not feasible, consider implementing temporary workarounds. Restrict access to the FileManager API endpoints to only authorized administrators. Implement strict input validation on the base_folder parameter to prevent path traversal attempts. Consider using a Web Application Firewall (WAF) to filter requests containing suspicious path manipulation patterns. Monitor access logs for unusual file access patterns.