Hostking Nigeria — web hosting and domains

How WordPress sites actually get hacked

Almost never by someone targeting your business. WordPress powers a huge share of the web, so automated bots scan continuously for known vulnerabilities and weak logins. You are not being singled out — you are being scanned, along with everyone else.

  • Outdated plugins and themes — by far the most common route
  • Weak or reused admin passwords — brute-forced in bulk
  • Nulled premium plugins — malware ships inside them deliberately
  • Abandoned installs — the test site nobody updates for two years
How WordPress sites actually get hacked

Lock down the login

The wp-login page is the single most attacked URL on any WordPress site. These steps remove most of that risk in under half an hour.

  • Never use “admin” as a username — it halves the work for an attacker
  • Use a generated password, unique to this site
  • Enable two-factor authentication on every administrator account
  • Limit login attempts so brute-force runs get blocked
  • Consider changing the login URL — obscurity is not security, but it does cut bot noise
Lock down the login

Users and permissions

Every administrator account is a full set of keys. Most sites have more of them than they need, often belonging to people who left years ago.

  • Give each person the lowest role that lets them work — Editor, Author, Contributor
  • One administrator is usually enough; two is plenty
  • Remove accounts when someone stops working on the site
  • Check the user list periodically for accounts you do not recognise
  • An unexpected admin account is a strong sign of compromise
Users and permissions

File and configuration hardening

A few server-side settings close off the routes that automated attacks rely on. If any of this is unfamiliar, ask us rather than guessing.

  • Set file permissions to 644 and directories to 755
  • Set wp-config.php to 640 — it holds your database credentials
  • Disable file editing in the dashboard by adding define('DISALLOW_FILE_EDIT', true); to wp-config.php
  • Disable PHP execution in the uploads folder
  • Keep no backup .zip or .sql files in a web-accessible directory
File and configuration hardening

What your hosting should be doing

Some protection belongs at server level, where it works regardless of what happens inside WordPress. This is included on every Hostking plan rather than sold as an add-on.

  • Imunify360 — scans for malware and blocks known attack patterns before they reach your site
  • Server firewall — filters malicious traffic at the network edge
  • JetBackup — daily backups so a bad day is recoverable
  • Free SSL — encrypts traffic, and browsers now expect it
  • Server-level protection keeps working even if a plugin fails or you forget an update
What your hosting should be doing

Get Online with Hostking

Hosting from ₦1,325/month billed annually, with a free domain, free SSL, business email and daily backups included. Choose Starter or above and we design your website free — no agency fee, no contract.

See hosting plans Talk to our team

Hostking support team

How to Secure a WordPress Site — Common Questions