What the public record says
Wordfence Intelligence lists the Sideblog plugin as removed and records CVE-2022-1787, described as cross-site request forgery leading to settings update and stored cross-site scripting in versions up to and including 6.0. The record marks the vulnerability unpatched. Open the Wordfence record ↗
If Sideblog is installed
- Confirm the plugin slug and files. Do not rely on a display name alone.
- Create a tested backup. Preserve the database and files before changing production.
- Identify the asides category. The posts themselves may remain usable after deactivation.
- Build replacement output. Use a Query Loop, theme template or maintained custom solution.
- Deactivate and remove the code. Validate archives, feeds and short-post URLs afterward.
- Review accounts and logs. Removal prevents future exposure but does not prove that no earlier compromise occurred.
Do not confuse removal with cleanup
Deleting a vulnerable plugin closes one code path. It does not remove unexpected administrator accounts, injected JavaScript, modified themes or malicious scheduled tasks that may already exist. Compare the site against known-clean sources and rotate credentials when compromise is suspected.
Frequently asked questions
Is Sideblog safe to install on a live site?
The current public record lists the plugin as removed and the reported issue as unpatched. It should not be installed on a public production site.
Will deactivating Sideblog delete aside posts?
The historical model used ordinary posts in a category, so deactivation should not inherently delete those posts. Back up first and verify the specific installation.