Securing WordPress in 2026 comes down to three habits: scan what you actually expose, reduce it, and monitor what is left. Most compromises do not start with a novel exploit against WordPress core. They start with an abandoned plugin, a reused admin password, or a database backup sitting in the web root. A regular WordPress security scan plus a short hardening list removes the majority of practical attack paths.
Why this matters for your website
WordPress runs a very large share of the web, so attacks against it are automated and indiscriminate. Bots crawl for known plugin versions, probe wp-login.php, and retry credential lists. Your site does not need to be interesting to be targeted; it needs to be reachable.
The business cost is rarely the defacement. It is the SEO damage from injected spam, the payment data exposure on WooCommerce, the hosting suspension, and the days spent rebuilding from an unverified backup.
The WordPress attack surface
- Core — rarely the weak point, but unpatched majors stay vulnerable for years.
- Themes and plugins — the dominant source of known vulnerabilities, especially abandoned or nulled code.
- wp-login.php and XML-RPC — credential stuffing and, via
xmlrpc.php, amplified multi-call brute force. - REST API user enumeration —
/wp-json/wp/v2/userscan leak valid usernames. - wp-config.php, backups and repos —
.sqldumps,.env, and exposed.gitdirectories hand over credentials. - File permissions and uploads — writable directories that allow PHP execution turn a file upload into shell access.
- Hosting — shared accounts, stale FTP/SFTP users, and outdated PHP versions.
Scanning: what a WordPress vulnerability scanner checks
A WordPress vulnerability scanner works mostly by fingerprinting, then matching versions against a vulnerability database such as WPScan or the NVD.
- Version disclosure — the
generatormeta tag,readme.html, and?ver=query strings on CSS and JS assets. - Component inventory — installed plugins and themes with versions, then correlation to known CVEs.
- Exposure checks — user enumeration, directory listing, exposed backups,
.git, and debug logs.
Read results by confidence, not count. Version-based findings are inferences and can be false positives when your host backports patches, while a confirmed exposed file is fact. Fix confirmed exposures first, then patch inferred vulnerabilities by updating.
Hardening in order of impact
Work down this list. The first four items close more real attack paths than everything below them combined.
- Updates — Risk: known exploits. Check: Dashboard → Updates. Fix: enable auto-updates for core minors and plugins; review majors monthly.
- Unused plugins and themes — Risk: vulnerable code still reachable when deactivated. Check: plugin list. Fix: delete, do not deactivate.
- Admin authentication — Risk: credential stuffing. Check: user list for
adminand shared logins. Fix: unique passwords in a manager, 2FA on every administrator. - Login rate limiting — Risk: brute force. Check: server logs for repeated POSTs to
wp-login.php. Fix: rate limit at the WAF or server; lock out after failed attempts. - XML-RPC — Risk: amplified brute force and pingback abuse. Check: request
/xmlrpc.php. Fix: block it at the server unless Jetpack or a mobile app needs it. - Security headers — Risk: clickjacking, XSS impact, referrer leakage. Check: response headers. Fix: set CSP, HSTS, X-Content-Type-Options, Referrer-Policy and Permissions-Policy in nginx or Apache, not a plugin.
- Roles — Risk: over-privileged accounts. Check: Users screen. Fix: editors and authors by default; two administrators maximum.
- Backups — Risk: unusable or publicly readable backups. Check: try a restore to staging. Fix: off-server storage, never inside the web root.
- File permissions — Risk: writable code directories. Check:
wp-config.phpat 640 or stricter. Fix: disable file editing withdefine('DISALLOW_FILE_EDIT', true);.
Header syntax and trade-offs are covered in our guide to HTTP security headers; the official WordPress hardening documentation covers file layout in detail.
Monitoring after you harden
- File integrity — alert on changes to core files,
wp-config.phpand the uploads directory; injected PHP in/wp-content/uploads/is a classic sign. - Uptime and TLS — monitor availability and certificate expiry, which causes more outages than attacks do.
- Search Console — enable email alerts for Security Issues and manual actions to catch SEO spam early.
- Log review — watch weekly for login failures, 404 bursts against plugin paths, and unexpected admin user creation.
How to check your own site
Start free and unauthenticated. Run the free website security check to see what an attacker sees in a first pass: TLS configuration, headers, and obvious exposures.
Scantinel (scantinel.ai) is an automated website security assessment platform that runs OSINT, network, and OWASP Top 10 web vulnerability tests against ownership-verified assets and delivers actionable, business-owner-legible reports. For WordPress specifically:
- The Essential scan passively detects the WordPress version, known-vulnerable plugins, security headers, cookie flags and exposed common files in minutes.
- The Full scan adds a WordPress and WooCommerce deep scan using WPScan with its vulnerability database, plus active OWASP Top 10 testing, supply-chain checks for exposed
.gitand.env, and port and service fingerprinting.
Scans only run against assets you have verified ownership of, and they are non-destructive. An automated scan is not a penetration test: it finds known and detectable issues, not bespoke business-logic flaws. You can run a WordPress security scan when you are ready, or read how to check your website security manually first.
Key takeaways
- Plugins and themes, not core, cause most WordPress compromises; delete what you do not use.
- Treat version-based scan findings as inferences and confirmed exposures as facts, and fix the facts first.
- Put 2FA on every administrator and rate limit
wp-login.phpat the server or WAF. - Set security headers in your web server configuration so they survive plugin changes.
- Test a restore from backup; an untested backup is a plan, not a control.
Frequently asked questions
How do I scan my WordPress site for vulnerabilities?
Run an external scan that fingerprints your WordPress version, plugins and themes, then matches them to a vulnerability database such as WPScan. Combine it with checks for exposed backups, .git directories and user enumeration. Repeat monthly and after every major plugin change.
Do I need a security plugin for WordPress?
A security plugin is useful for login rate limiting, 2FA and file integrity alerts, but it cannot fix an unpatched plugin or a misconfigured server. Keep one, keep it updated, and do not rely on it for headers or WAF filtering, which belong at the server or CDN layer.
How do hackers get into WordPress sites?
Most intrusions come from three routes: a known vulnerability in an outdated plugin or theme, guessed or reused administrator credentials, and exposed files such as backups or configuration dumps. Automated bots find all three at scale. Patching, 2FA and removing exposed files close the common cases.
Where to go next
For the layers beyond the CMS, including DNS, email authentication and TLS, see the complete website security guide.
Published January 2026 by the Scantinel Security Research Team. Security guidance changes: verify current details against primary sources such as OWASP, NVD and WPScan.
Comments
No comments yet.