If you opened your shop's website this morning and something is wrong — a weird login screen, a page you didn't write, customers saying Google warned them off — don't panic, and don't start clicking random "free malware cleaners."
This is a first-aid guide for a Main Street owner, not a developer. It assumes a simple WordPress site: your name, your services, a contact form, maybe a few products.
Two honest things up front.
First, nobody can promise your site will never have a problem again. Anyone who says "hack-proof" is selling you something.
Second, you did not fail as a business owner because you didn't spend Sunday night reading security bulletins. In 2025, Patchstack recorded 11,334 new vulnerabilities in the WordPress ecosystem, and 91% of them were in plugins. Almost half didn't have a fix from the developer at the moment they were made public. For the holes attackers actually piled onto, Patchstack's weighted median time to first exploit was five hours. That's not a homework assignment for a plumber.
Sources for those figures: Patchstack, State of WordPress Security in 2026.
What a hack usually looks like
It isn't always a Hollywood "the site is down" moment. In the attacks that were documented in public this year, the pattern was often quieter:
- A new administrator account you didn't create
- A PHP file sitting in an uploads folder where only photos or form attachments should be
- Password-reset emails stolen out of a log, then used to take over the admin account
- A page that looks fine to you and ugly or dangerous to a customer
In August 2026, a critical file-upload flaw in Elementor Pro (CVE-2026-32475) was exploited the same day it was disclosed. Elementor Pro is a plugin with more than 6 million active installations. Attackers used a form's file-upload field to plant a PHP file and run commands on the server. Wordfence later said it blocked more than 190,000 exploitation attempts. Source: BleepingComputer, September 3, 2026.
Around the same stretch, Super Forms had a critical upload bug (CVE-2026-14894) that let unauthenticated attackers plant backdoors. Wordfence reported blocking more than 250,000 exploit attempts. Source: The Hacker News, September 4, 2026.
In November 2025, attackers used a flaw in the Post SMTP plugin (CVE-2025-11833), installed on more than 400,000 WordPress sites, to read email logs — including password-reset links — and hijack administrator accounts. Wordfence said attacks started November 1, 2025, and that it had blocked over 4,500 attempts. Source: BleepingComputer, November 4, 2025.
That's what "a WordPress hack" often is in real life: a plugin hole, a file or a login that shouldn't be there, and a shop owner who finds out late.
Do this today, in this order
1. Don't keep poking the live site as the admin. If you suspect you are locked out, or you see a user you don't recognize, treat the site as hostile. Use a different computer or a private window only if you need to look. Don't enter your usual password into a page that looks "almost right."
2. Call your host and tell them you think the site is compromised. Ask them to take a snapshot of the site and the database right now, before anyone "cleans" anything. If the site is serving malware to customers, ask whether they can put up a temporary "we'll be back" page or take the site offline while you sort it out. A few hours of a down site is better than a week of customers hitting a bad page.
3. Change the important passwords, but only from a clean place. That means the hosting account, the domain registrar, the email inbox tied to the site, and the WordPress admin — once you have a clean way in. Use new passwords, not a variation of the old one. If you reused that password anywhere else, change those too.
4. Look at the user list. In WordPress, that's usually under Users. Any administrator you don't recognize should be treated as a problem. Don't just delete it and assume you're done. Write down the username and the date. Your host or a cleaner will want that.
5. Update WordPress, the theme, and every plugin — or have your person do it — after the snapshot. Several of the incidents above were exploited as soon as the flaw became public, including the same day. Waiting "until things calm down" is how a small hole stays open. WordPress core itself had a security release on July 17, 2026 (version 7.0.2) and turned on forced auto-updates because of the severity. Source: WordPress.org, July 17, 2026. Another core security release, 7.1.4, shipped on October 28, 2026, including a weakness in the upgrade process that can lead to remote code execution during the upgrade window. Source: WordPress.org, October 28, 2026.
6. Delete plugins and themes you don't use. Every unused plugin is still code on the server. A lot of the risk in the Patchstack numbers lives in plugins, not in "WordPress" as a brand.
7. Have someone who knows what they're doing search for leftover files. In the Elementor Pro case, the tell was a PHP file in the form-uploads folder, where PHP files should not be. A cleaner will look in wp-content/uploads, in plugin folders, and for new admin users. This is the step most owners should not freelance.
8. Tell the people who need to know. If customer data, payments, or form submissions may have been exposed, you may have a legal duty to notify. This article is not legal advice. If that might be you, talk to an attorney and your payment provider.
9. Don't pay a ransom and don't hire the first Google ad that says "we can unhack you in 20 minutes." Use your host, a person you already trust, or a known WordPress security company. Take the snapshot first so you have a rollback.
What not to do
Don't ignore it because "the homepage looks fine now." Some malware hides from the owner and shows itself to customers or to search engines.
Don't rebuild on top of a dirty install and call it a fresh start. If the bad files are still there, you just built a new storefront on a bad foundation.
Don't assume a security plugin badge in the sidebar would have saved you. Some of the 2026 attacks were exploited within hours of disclosure. Updates, backups, and fewer plugins still matter more.
After the fire is out
Once the site is clean, the boring work is what keeps you from doing this again:
- Automatic backups you have actually tried to restore
- Automatic updates, or a person whose job is to run them
- A short plugin list
- A current version of PHP. PHP 8.1 reached end of life on December 31, 2025. Older branches have been unsupported for years. Source: php.net/eol.php.
- New passwords and, if you can, two-factor login on the admin account
That list is also the honest problem with WordPress for a busy shop: the software can be fine, and it can still turn you into a part-time systems administrator. In October 2026, PHP released critical security updates for every supported version and said "updating is the only safe choice." Source: PHP 8.5.12 announcement, October 21, 2026. This is going to keep coming.
A simpler option, if you're tired of being the webmaster
If your site is a simple business site, and the thing you actually want is to stop living in this cycle, that's the problem InLink was built for.
Link is the AI web developer at inlink.com. You give it your URL. It copies or moves your site — up to 50 pages — with a URL, forms, and a leads inbox. You change the site by asking. You don't babysit plugins. It's $99 a year, with no monthly bill; extras such as a domain name are priced before you buy. Code INLINKBETA makes the first 6 months free while its uses last.
It will not un-hack a site that is already compromised. Do the first-aid steps above, or have a professional clean the current site, before you move anything. Then, if you want a web guy who's always there instead of a weekend chore, send InLink the link and go from there.
You're a shop owner. You shouldn't have to be a WordPress incident responder too.