On 22 September 2026, WordPress shipped a security update. The same day, the security company Patchstack counted the first attempts to exploit the hole it closed. In 2026 that was not an outlier but the rule: between “vulnerability published” and “vulnerability exploited” there are often only hours. Here is what happened, why small businesses get hit and how to protect your website.
In short
- Attacks often start within hours of a security update, not weeks.
- The most common way in is an outdated plugin or theme, less often WordPress itself.
- Modern stacks like Next.js need regular updates too. We patched our own site twice in November.
- Website maintenance is not an extra. It is the part that keeps your site running.
What happened in 2026
WordPress itself: a hole in page templates
WordPress 7.1.2 closed a vulnerability (CVE-2026-87902) that let attackers without a login make WordPress load an arbitrary PHP file on the server. Under certain conditions this allowed running their own code, which means taking over the site. The WordPress team rates it critical. The key condition: the active theme has a folder whose name starts with “page-”. That applies to the older default themes Twenty Twelve and Twenty Fourteen, and to popular themes such as Neve, Hestia and Sydney.
Patchstack saw the first attempts on the day of the update, and by the next day attackers were already trying to write files to servers. On 25 September the US cybersecurity agency CISA added it to its catalogue of actively exploited vulnerabilities. The good news: the fix was shipped back to version 4.7, and WordPress installs minor security updates on its own by default, unless someone switched that off.
Plugins: Bricksforge and Modular DS
Bricksforge is an add-on for the Bricks page builder. Up to version 3.1.8.9, anyone could upload files without logging in and run code on the server, the highest severity there is. Patchstack has seen attacks since 7 October. Version 3.1.8.10 fixes it.
Modular DS is a tool agencies use to manage many WordPress sites from one place, installed on more than 40,000 sites according to Patchstack. Up to version 2.5.1, attackers could gain administrator rights without a login, and this one was actively exploited too. That is the bitter twist of the year: a maintenance tool became the way in. Maintenance needs maintenance as well.
Not just WordPress: Next.js and React
Not running WordPress does not get you off the hook. Next.js, the framework this website runs on, had several security advisories this autumn. On 14 October a critical flaw in image optimisation that allowed code execution with SVG files. On 3 November seven more of medium severity, mostly around caching: under some conditions one user’s cached data could end up with another. On 10 November came a critical flaw in React Server Components which, according to the React team, only affects very rare setups but should still be patched right away.
| Software | Type of flaw | Severity | Fixed in |
|---|---|---|---|
| WordPress | File inclusion without login, code execution under conditions | critical (9.2) | 7.1.2, backported to 4.7 |
| Bricksforge | File upload and code execution without login | critical (9.8) | 3.1.8.10 |
| Modular DS | Administrator rights without login | critical (9.8) | 2.5.2 |
| Next.js (October) | Code execution via SVG image optimisation | critical (9.5) | 16.4.1 and 15.5.28 |
| Next.js (November) | Seven cache and data leaks | medium (6.0–6.9) | 16.4.5 and 15.5.29 |
| nodemailer | Injected commands when sending mail | low to medium | 8.0.5 |
Severity as a CVSS score from 0 to 10, as published by the vendor or the US National Vulnerability Database (NVD).
Why small businesses get hit
Nobody is hunting for your joinery’s website in particular. Attackers run programs that scan the web around the clock for known plugin names and version numbers. If you run an outdated version, you will be found, however small the business. That is why attacks come so fast: as soon as a flaw is public, it gets added to those scanners.
What follows is often noticed late:
- Spam: your server sends bulk mail, and afterwards your real emails land in spam folders.
- SEO spam: hidden pages or links for someone else’s products that damage your Google ranking.
- Google warning: search results show a note that the site may be hacked. Hardly anyone clicks after that.
- Redirects: visitors end up on scam pages, often only on mobile so the owner does not notice.
- Data protection: if customer data is affected, for example from forms, the breach usually has to be reported to the data protection authority within 72 hours.
Is your website affected?
You can get a rough answer in a minute. Our free website security check matches your site's WordPress, plugins, PHP and server against known vulnerabilities, without attacking anything, and shows what turned up in the last month around Linux, Docker and co. You see the result right away, and we send you a detailed review in person.
How we patch our own site
This website runs on Next.js and sends form submissions through the nodemailer library. Both were affected this autumn. On 9 November we moved Next.js to 16.4.5, closing the October and November advisories and the React flaw. In the same step nodemailer went from version 7 to 10.4, which among other things closed the flaws that allowed injecting commands into outgoing mail. On 20 November another advisory followed, and we moved to 16.4.6.
This is how it runs every time:
- Read the advisory: which versions are affected, under which conditions?
- Check: does the site use the affected feature at all? That decides how urgent it is, not whether we update.
- Update and build: apply the update, rebuild the whole site, re-check all dependencies for known flaws.
- Test: click through the home page, both languages, redirects, the sitemap and the forms.
- Ship: only then does the new version go live.
It is unspectacular, and that is the point. Maintenance is a routine that happens regularly, not something you do once things are on fire.
Checklist: how to protect your website
- Stay current: update WordPress, plugins and themes regularly, and let security updates install automatically.
- Clean up: delete unused plugins and themes instead of just deactivating them. Deactivated code still sits on the server.
- Backups: regular, stored somewhere other than the website, and restored at least once as a test.
- Access: strong passwords and two-factor login for every admin. Remove former staff and previous agencies.
- Ownership: one person or company that reads security advisories and acts on them. “Someone” is nobody.
- Basics: HTTPS with a valid certificate, and a server that doesn't give away version numbers.
- Age: if your site can no longer be updated without something breaking, that is one of the clear signs it needs a relaunch.
Website hacked: what now?
- Do not delete things in a hurry. The traces show later how the attacker got in.
- Tell your hosting provider or agency and take the site offline or into maintenance mode if needed.
- Change every password: WordPress, hosting, FTP, database and email.
- Restore a clean backup from before the attack and update everything immediately afterwards.
- Close the way in. Otherwise the attacker is back within days.
- Check Google Search Console and request a review after the clean-up if a warning is shown.
- Sort out data protection: if customer data was affected, check whether you must report it to the authority within 72 hours.
Conclusion
A website is never secured once and for all. It is as safe as its last update. 2026 showed that attackers are faster than ever, and that it barely matters whether a site belongs to a corporation or a family business. If updates, backups and ownership are handled properly, you are still ahead of the vast majority of attacks. What that costs on an ongoing basis is covered in What does a website cost in 2026?
Rather not follow security advisories yourself? We take care of updates, backups and monitoring for your site. Website maintenance at visualy
Sources
WordPress advisory on CVE-2026-87902, Patchstack on the first attacks, CISA Known Exploited Vulnerabilities catalogue, Patchstack on Bricksforge, Patchstack on Modular DS, Next.js security advisories, React security advisory, nodemailer security advisory. As of 20 November 2026.

