Plugin & theme remediation — high-level pointers (local fallback)

watchog’s audit tells you what is wrong. The detailed, current fix procedures — safe update order, rollback/backup steps, replacement shortlists, vulnerability triage — live in the team wiki (set OUTLINE + OUTLINE_API_URL and the report links them directly). This file is the minimal high-level fallback for when the wiki isn’t configured: direction only, deliberately not step-by-step, so there’s no detailed content to drift out of sync with the wiki.

• Outdated plugins — take a backup, update on staging first, then production; re-test the affected pages afterwards. Prioritise the largest version drift.
• Abandoned plugins — no update in a long time is a standing risk; find a maintained replacement or remove the plugin if the feature is no longer needed.
• Known vulnerabilities — treat as urgent; update to the fixed version, or if none exists, disable or replace the plugin until it’s patched.
• Lagging WordPress version — a plugin/theme untested against current WordPress may break on core updates; verify compatibility before upgrading core, and update or replace what’s incompatible.

Full playbook → the team wiki’s WordPress maintenance reference (update order, rollback, replacement shortlists, vulnerability triage). Configure the wiki to have watchog surface the live versions in its report.