Description

Author Arbitrary File Deletion in WEBO MCP <= 3.0.18 versions.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "6.8",
  "pubDate": "2026-09-30T13:17:36.030Z",
  "pubdate": "2026-09-30T13:17:36.030Z",
  "executiveSummary": "WEBO MCP versions 3.0.18 and earlier contain an arbitrary file deletion vulnerability that permits unauthorized actors to remove files from the underlying filesystem.\nThe vulnerability is classified as an improper neutralization of special elements used in a pathnames (Path Traversal/Arbitrary File Deletion).\nAn unauthenticated or authenticated attacker with minimal access can exploit this flaw to disrupt system availability, cause service instability, or delete critical configuration files.\nThis vulnerability poses a significant risk to system integrity and operational continuity. By manipulating file path parameters, a remote attacker can delete sensitive files that the application process has permissions to access.\nNo specific user interaction is required for successful exploitation, assuming the attacker has network access to the target endpoint.",
  "technicalDetails": "The vulnerability resides in the way WEBO MCP handles user-supplied input intended for file system operations, specifically within file deletion functionality.\nThe root cause is an insufficient validation of directory path parameters, which allows for path traversal sequences (e.g., '../') to be injected into file manipulation functions.\nWhen an attacker provides a crafted request, the application fails to properly sanitize or constrain the target directory, enabling the traversal out of the intended directory structure.\nExploitation occurs when the application processes a request containing a malicious file path. If the web server process runs with sufficient privileges, the attacker can target critical system files, application configuration files, or other sensitive data structures.\nThe attack flow generally involves the following stages: First, the attacker identifies the API endpoint or web interface component responsible for file management. Second, the attacker crafts a malicious request string incorporating path traversal sequences designed to target specific file locations on the server. Third, the attacker submits this request to the vulnerable endpoint. Finally, the application, failing to sanitize the path, proceeds to execute the file deletion command on the resolved, traversed path.\nThis vulnerability is particularly impactful because it does not require complex payloads; simple path manipulation often suffices to bypass the lack of input validation. The post-exploitation impact includes potential denial-of-service, as the removal of core application dependencies can prevent the service from initializing correctly. Furthermore, it may facilitate secondary exploitation vectors if specific security-related files are removed.\nGiven that this vulnerability affects WEBO MCP <= 3.0.18, any deployment utilizing these versions is susceptible to local file system compromise regardless of the operating system, provided the filesystem permissions allow the application process to perform deletions at the targeted paths."
}