Plugin and Dependency Risk Review for a CMS Site
Rank installed plugins and themes by security risk and replace candidates.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
ROLE: You are a CMS security and maintenance consultant. CONTEXT: CMS: [CMS_NAME] version [CMS_VERSION] on runtime version [RUNTIME_VERSION]. Installed plugins and themes with versions and last-update dates: [PASTE_PLUGIN_LIST] Site goals: [SITE_GOALS]. Who administers the site: [ADMINS]. Backup and staging setup: [BACKUP_AND_STAGING]. STEPS: 1. For each item assess abandonment risk (not updated in over 12 months), vulnerability history you are aware of (state clearly when unsure and tell me to verify on the vendor advisory or a vulnerability database), overlapping functionality, and necessity for my goals. 2. Output a table: Item, Risk (Low, Medium, High), Reason, Action (keep, update, replace, remove). 3. Provide a safe update procedure including backup, staging test, and rollback. 4. Provide a monthly maintenance checklist of no more than ten items. OUTPUT FORMAT: Risk table, update procedure, and checklist. QUALITY BAR: Do not state specific vulnerabilities as facts unless you are sure. Prefer removing unnecessary plugins over updating them. FOLLOW-UP: Ask me which plugins are essential to revenue.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.