 The harm of malicious inputs often depends on insufficient access controls and the failure to track authorization across plugins.  Inadequate access control allows a plugin to blindly trust other plugins and assume that the end user provided the inputs.  Such inadequate access control can enable malicious inputs to have harmful consequences ranging from data exfiltration, remote code execution, and privilege escalation.  This item focuses on the creation of LLM plugins rather than using third-party plugins, which is covered by LLM-Supply-Chain-Vulnerabilities.  Common Examples of Vulnerability A plugin accepts all parameters in a single text field instead of distinct input parameters A plugin accepts configuration strings, instead of parameters, that can override entire configuration settings A plugin accepts raw SQL or programming statements instead of parameters Authentication is performed without explicit authorization to a particular plugin A plugin treats all LLM content as being created entirely by the user and performs any requested actions without requiring additional authorization