Many plugins require configuration with sensitive data such as API keys, passwords, etc. When implementing these plugins, this sensitive data is stored using functions such as
It would be trivial to write a trojan plugin that provides a useful function but also performs a variety of
get_option() calls on known-sensitive options. Even if this isn't possible, a manual SQL query can reveal this sensitive data.
Is there any way to avoid this inherently insecure model?