Website Animation: Types, Tools and Performance Without Compromise
Website animation done right: micro-interactions, scroll animation, Lottie, CSS, GSAP and WebGL, plus how to protect speed, Core Web Vitals and accessibility.
Read
To secure WordPress, do five things in this order: keep core, plugins and themes updated and delete the ones you don’t use; keep only the admin accounts you need, with strong passwords and 2FA; set up automatic backups stored off the server; tighten file permissions and turn off code editing in the dashboard; then add a WAF and change monitoring. Most hacks don’t start in WordPress core; they start in plugins. According to Patchstack, 91% of the 11,334 new vulnerabilities found in 2025 were in plugins, and just 6 were in core.
The clearest picture comes from the annual Patchstack State of WordPress Security in 2026 report. In 2025, 11,334 new vulnerabilities were found in the WordPress ecosystem, 42% more than the year before. 91% were in plugins, 9% in themes, and core had 6 low-priority issues. A few more numbers from the report explain why “our WordPress is up to date” isn’t enough:
Patchstack sells security services, so read the report with that in mind, but the direction is clear. Attackers come in through plugins, they move fast, and your host won’t stop everything.
| Common attack route | How to defend against it |
|---|---|
| A vulnerable or abandoned plugin or theme | Updates, fewer plugins, vulnerability monitoring, a WAF with virtual patching |
| A guessed or stolen admin password | Unique passwords from a manager, 2FA, login rate limiting |
| “Free” copies of paid plugins (nulled) | Plugins and themes only from WordPress.org or the developer |
| Over-broad file permissions and the dashboard code editor | 755/644 permissions, DISALLOW_FILE_EDIT |
| Poorly isolated hosting, unencrypted FTP | Hosting with account isolation, SFTP or SSH instead of FTP |
This list is based on the official Hardening WordPress guide and related WordPress documentation, plus what we check on client sites ourselves.
wp-config.php with the official WordPress.org generator. Change them whenever you suspect a breach: it invalidates every active session, including the attacker’s.wp-config.php and .htaccess.wp-config.php 440 or 400 so other users on the server can’t read it. Never 777, not even for the uploads folder (WordPress: file permissions).define( 'DISALLOW_FILE_EDIT', true ); to wp-config.php to disable the plugin and theme editor in the dashboard. The docs point out it won’t stop someone uploading malicious files, but it closes the easiest route to changing code after an account takeover.wp-content/uploads. That folder is for images and documents, not scripts./xmlrpc.php and /wp-login.php.wp core verify-checksums compares core files against WordPress.org checksums, and wp plugin verify-checksums does the same for plugins from the official directory.| How often | Task |
|---|---|
| Continuously (automated) | Core security updates, backups, WAF, uptime and new-account monitoring |
| Weekly | Plugin and theme updates, checking that backups ran, reviewing alerts |
| Monthly | Reviewing users and roles, removing unneeded plugins, verifying checksums, Search Console reports |
| Quarterly | A test restore from backup, reviewing file permissions and server configuration, rotating technical account passwords |
| After any incident | New passwords and salts, an account review, full verification of files and database, root-cause analysis |
In November 2026 we cleaned up our own site after a hack. I’m writing about it openly because it shows what a typical spam infection looks like and why “just delete the suspicious files” doesn’t cut it. Here’s what we found:
We removed the injected code from both files, deleted the rogue account and purged the spam posts and terms from the database. The spam URLs now return 410 Gone. Google treats all 4xx codes except 429 the same way and drops such URLs from the index if they were indexed before (Google Search Central). We chose 410 because it tells every crawler unambiguously that the page is gone for good.
The lessons match the Patchstack report, which notes that malicious code increasingly lands inside genuine core, plugin or theme files rather than in separate, easy-to-spot files. That’s why our cleanups compare files against checksums and clean copies and go through the user list and the database, instead of just hunting for oddly named files.
This article is about prevention, but if you’re seeing signs of a hack, the order of steps matters:
If you’d rather not do it yourself, see how our WordPress malware removal works. Keep an eye on search traffic too: injected spam damages visibility, and checking the site after an incident is a good moment for an SEO audit.
The worst answer is “everyone”, because then nobody is. Most of the neglect we see isn’t about lack of knowledge; it’s that after launch nobody was given the job of checking updates, backups and accounts every week. If no one in the company will do that, hand it to a provider with a clear scope: what runs automatically, what’s done by hand, how often and who responds to an alert.
Want someone to keep an eye on updates, backups and security for your site? Take a look at our WordPress maintenance, and if your site is already infected, get in touch and describe what you’re seeing.
Keep core, plugins and themes updated and delete the ones you don’t use. Keep only the admin accounts you need, with strong passwords and 2FA, set up automatic off-server backups, tighten file permissions and disable the dashboard code editor. Then add a WAF and monitoring for file and account changes.
Core is: in 2025 Patchstack found only 6 low-priority vulnerabilities in it. The problem is plugins and themes, which accounted for the rest of the 11,334 new flaws. How secure a WordPress site is depends mainly on how many plugins you run, which ones, and how quickly you update them.
Yes, if you don’t use it. The WordPress documentation recommends disabling XML-RPC when it isn’t needed, and otherwise restricting and rate-limiting it. Some mobile apps and older integrations rely on it, so check before you switch it off.
The WordPress docs suggest weekly backups for smaller sites and daily ones for busy sites, and always before an update. Backups must include both the database and the files. Keep 3–5 recent copies in different places and regularly check that you can actually restore from them.
Check your administrator list, the Security Issues report in Search Console and whether the number of indexed pages has grown for no reason. Compare files against checksums with wp core verify-checksums. Spam is often visible only in the page source, for example hidden links in the footer.
No. A plugin helps with things like 2FA, login limits and file scanning, but it can’t replace updates, backups, sensible permissions and tidy accounts. Patchstack notes that the most exploited flaws look like normal logged-in traffic, so generic filters won’t stop them.
Insights

Website animation done right: micro-interactions, scroll animation, Lottie, CSS, GSAP and WebGL, plus how to protect speed, Core Web Vitals and accessibility.
Read
Elementor vs a custom WordPress theme: speed, SEO, security, cost and editing. When a page builder is enough, and what leaving Elementor did for our own site.
Read
How to write a website brief: a template to copy covering goals, audience, competitors, content, features, SEO, integrations, budget and timing, plus mistakes.
ReadWe design and code company websites from scratch — no off-the-shelf templates, built for conversion, speed and visibility in Google and AI search.
We use essential cookies and, with your consent, analytics (Google Analytics, Hotjar) and marketing cookies to understand how you use the site and improve it. Details in our privacy policy.