The vulnerability lies in several Express.js route handlers within src/endpoints/extensions.js. The core issue is a path traversal vulnerability stemming from improper handling of the extensionName parameter in the request body. The application used a weak check (if (!request.body.extensionName)) to validate the extensionName. A malicious user could provide . as the extensionName. This value is truthy and passes the check. Subsequently, the sanitize-filename library, when processing . returns an empty string. When this empty string is used with path.join(basePath, ''), the result is the basePath itself. This allowed an attacker to perform actions, such as deletion, on the parent directory (extensions) instead of a specific extension's subdirectory. The patch addresses this by checking the result of the sanitization, ensuring that an empty sanitized name is rejected. This vulnerability affected the /api/extensions/delete, /api/extensions/update, /api/extensions/branches, /api/extensions/switch, and /api/extensions/version endpoints.