Skip to content
// wordpress

WordPress security monitoring, explained in plain English

WordPress itself is well maintained. The risk usually sits in what's added to it: plugins, themes and settings that nobody has looked at since the site launched. Odesstra keeps track of what your WordPress site visibly runs, tells you when a published flaw affects it, and has a web developer fix it if you want. It's a service run by a person: book a call, and we take it from there.
// why it needs watching

Why WordPress sites need someone keeping an eye on them

A typical small-business WordPress site has a theme, a page builder, a contact form, an SEO plugin and a handful of others. Each is written by a different team and updated on a different schedule. When a flaw is found in one of them, it's published as a CVE or advisory, and attackers' tools start looking for sites that run the affected version, often within days.

The problem isn't that WordPress is weak. It's that nobody has the job of knowing what's installed and whether it's affected. That's the job we do.

// what we watch

What we keep track of

  • WordPress core version, from the generator tag and other visible signs.
  • Plugins and themes that can be identified from your public pages, with versions where they're visible.
  • Server software such as PHP, Apache or nginx, when your site advertises it.
  • The outside basics: your certificate, security headers and email protection, checked monthly.

We match that inventory against published vulnerability advisories. When something matches, you get a plain answer, not a feed of codes:

// hacker view

advisory: <contact-form plugin> · stored XSS · fixed in a newer release · site runs an older version affected

// plain english

Your contact form plugin has a known flaw. Someone could hide a malicious script in a form submission. Update it to the latest version today; it takes about five minutes.

// deeper checks

Authorised scans, only with your permission

On Care we also run regular external scans aimed at common WordPress problems, such as exposed configuration or outdated components. These only start after you prove you own the site (a DNS TXT record, a file in /.well-known/ or a meta tag) and sign a written authorisation. Scans use safe settings and never try passwords or take data.

// fixes

Updates and fixes by a developer who builds WordPress sites

Odesstra is run by a web developer in Gqeberha who builds and fixes websites, including WordPress. When a report or a heads-up from us needs action, you get a fixed quote. Say yes and we take a backup, apply the update or fix, check the site still works, and re-check the finding. See website security fixes for how that works.

// questions

Common questions

Do you need my WordPress admin login?

No. Monitoring works from outside, so we never ask for your admin password. If you later want us to do fix work, we'll agree the safest way to get access for that job only.

Isn't a security plugin enough?

A good security plugin is worth having. But it runs inside the site it's protecting, it doesn't explain findings in plain English, and it won't fix anything for you. We work alongside it.

Can you see every plugin I have installed?

Only the ones that leave visible traces on your public pages. Some plugins can't be seen from outside, so we'll also ask you for a list when you join.

How do I know if my WordPress site has been hacked?

Common signs are redirects to spam, admin users you didn't create, unfamiliar files or plugins, and browser warnings. Our guide is my WordPress site hacked? lists the signs and what to do in the first hour.

What about WooCommerce shops?

Yes. Shops are a good fit, because they handle customer details and payments. The same monitoring applies, and we pay extra attention to checkout-related plugins.

Talk to a human