An alert from INCIBE, Spain’s national cybersecurity institute, concerns you when the plugin, theme or WordPress version listed under “Recursos afectados” (affected resources) is installed on your site and your version falls within the range the alert gives. To find out, you need two things: the alert, and a list of what your site runs with version numbers, which WordPress already shows you under Tools > Site Health. The first time, comparing the two takes about fifteen minutes and you don’t have to change anything.
A Tuesday in October, half past nine in the morning. Aceites La Herradura, let’s say that’s its name, is a small olive mill between Vélez and Comares. It sells oil and honey over the counter and, for a few years now, through a WooCommerce shop. The site was built in 2020 by an acquaintance. He got paid, left the password on a sticky note on the office monitor and moved away for work.
Someone in the local traders’ group chat forwards the owner a link to an INCIBE alert about a WooCommerce plugin, rated critical. He reads it on his phone, standing by the scales: a name in English, a version number and a recommendation. He doesn’t know whether that plugin is in his shop. Nor does he know which plugins he has, or how many, or who updates them, if anyone does.
That afternoon he digs out the sticky note and logs in to the dashboard. Next to Plugins there’s a little circle with a 7 in it. On the Plugins screen, two have automatic updates switched on and the rest don’t. The emails WordPress sends after each update have been going for years to an address the owner doesn’t recognise.
Nobody did anything wrong on purpose. The site works and the shop sells. What’s missing is a small habit: putting the alert next to the list and seeing whether they match.
Where does INCIBE publish alerts for businesses?
INCIBE has two places for alerts, and it helps to know which one is meant for you. The first is the business section, Protege tu empresa (“protect your business”), with its alerts page. Each alert carries its publication date and an importance level, and it is written for the person running the business. The second is the INCIBE-CERT alerts area, which is more technical. The business alerts say so themselves: your technical support can find the more technical solution there.
You don’t need to read every one as if it were about you. On the day we wrote this, the first alerts on the business list were for TeamViewer, D-Link routers, WatchGuard and Adobe, rated high or critical. There wasn’t a single WordPress alert on that first page. An alert only concerns you if it names something installed on your site.
So you don’t have to keep checking, the page has a link to subscribe to the alerts and another for the newsletters. The newsletter has the usual catch: it arrives in an inbox, and if it’s the inbox nobody reads, you might as well not have it.
An alert concerns you if the name and version match
The alerts we’ve opened all follow the same layout: date, importance, “Recursos afectados” (affected resources), description and solution. The line that decides it is the affected resources line.
One example from WordPress itself is the business alert dated 09/09/2021. It was rated importance 4, “Alta” (high), and affected “WordPress, versiones entre la 5.4 y la 5.8”, meaning versions 5.4 to 5.8. The solution was to update to 5.8.1 from the “Escritorio”, “Actualizaciones” menu (Dashboard > Updates in English) by clicking “Actualiza ahora” (update now). The alert also carried a warning that almost nobody reads: before updating the live site, test on a copy and check that everything still works.
A shop example is the INCIBE-CERT alert published on 30/05/2025 about the TI WooCommerce Wishlist plugin, the one that adds a wish list to an online shop. Importance 5, “Crítica” (critical). Affected resources: version 2.9.2 and earlier. According to the alert, an attacker could upload files to the server without logging in. On that date there was no fix, and the recommendation was to deactivate and uninstall the plugin.
Notice what the alert says and what it doesn’t. It isn’t about every WooCommerce shop, only the ones running that plugin in that version or an earlier one. And on that day the solution wasn’t to update, because no fixed version existed yet. That’s why the date matters: an alert tells you what was known on the day it was published.
The check itself is mechanical. You copy the exact name given in the alert, look for it in your list and compare the version. If the plugin isn’t there, the alert isn’t yours, even if it says critical. If it is there and your version falls within the range, it is yours. And if you can’t make sense of the version number, ask in writing.
The fifteen-minute check, without changing anything
You need the administrator username and password, a computer and a blank document with today’s date at the top.
Log in to the dashboard. INCIBE points out in its alerts that the address is usually your domain followed by /wp-admin. If you don’t have the password, or you don’t know whose account you’re logging in with, stop there. That is the first thing you’ve found out, and the most important.
Look at the menu on the left. According to the WordPress documentation on automatic updates, when a new version of a plugin or theme is available, a bubble with a number appears in the menu. Write that number down.
Open Dashboard > Updates. Everything pending is listed there together: WordPress, plugins and themes. Don’t click anything yet, for the reason INCIBE’s alert gave about testing on a copy first. Write down what’s pending.
Go to Tools > Site Health. According to the WordPress help page for that screen, it has two tabs. The first, Status, separates critical issues from recommended improvements. Among the critical ones it mentions having plugins waiting to be updated, and it gives a reason worth reading twice: plugins have deep access to your site.
The second tab, Info, is the list you were after. It shows the WordPress version, the number of users, the active theme and the active and inactive plugins. For each plugin it gives the version, the author and whether automatic updates are switched on. There’s a button to copy the whole thing to the clipboard. Copy it and paste it into your document: that is the list you check any alert against.
Go back to Plugins and look at the automatic updates column. Since WordPress 5.5 they are switched on plugin by plugin, and by default WordPress runs them twice a day. If you can’t see the column, the documentation gives two possible reasons: your WordPress is older than 5.5, or your hosting or a plugin has disabled the feature. Either one deserves a question.
That leaves email. By default, WordPress sends an email when a plugin or theme updates automatically, when an update fails, and when both happen at once. If you’ve never seen one, either there are no automatic updates or the emails are going to an inbox that isn’t yours.
You now have a dated document showing what your site runs and what state it’s in, and you haven’t changed a thing.
What to ask, in writing, of whoever maintains the site
If someone is paid to maintain the site, or built it and still holds the keys, there’s no need to argue about the technical side. Just ask for five things by email, so there’s a date on record:
- Who has administrator access, and which address WordPress emails go to. It should be a business address.
- Each month, a copy of the Site Health Info tab, so you can see the versions without logging in. And that unused themes are deleted, as the documentation itself recommends.
- Which plugins update automatically, which don’t, and why. Sometimes there’s a reason not to automate one; ask them to put it in writing.
- How they take a backup before updating, and how they roll back if something breaks. WordPress suggests having that rollback in place before switching on automatic updates.
- What they do when an INCIBE alert comes out: a dated reply saying whether the plugin is installed, in which version, and what has been done. Three lines are enough.
If the answer is silence, or a “don’t worry, it’s all fine” with nothing attached, you already know more than you did. It’s much like what we described with the Kit Digital website that ended up as a brochure: whatever is handed over and then left untended stays exactly as it was on handover day.
When you don’t need all this
Some sites don’t need this every week: the ones with few plugins, all updating automatically, no critical issues in Site Health, and WordPress emails reaching an inbox someone opens. If that’s you, repeat the check when the person maintaining the site changes, or when an alert arrives naming something that rings a bell.
Nor is there any need to panic at the word critical. A critical alert about a plugin you don’t have is news, not your problem. And if your site isn’t built on WordPress, this note isn’t for you.
If you suspect something has already happened, or you can’t tell whether an alert affects you, INCIBE runs 017, its cybersecurity helpline. It is free and confidential, also serves businesses and professionals, and is open from 8 am to 11 pm every day. You can call, message 900 116 117 on WhatsApp, use Telegram (@INCIBE017) or fill in a form.
If you’d rather we did it
If the check came back clean and whoever maintains your site answers the five questions, you don’t need us. If you’ve found that nobody knows whose password it is, that updates have been pending for ages, or that the shop relies on plugins nobody remembers installing, that’s where we can help. Presence (€1,490) is your business website rebuilt from scratch, with a clear person responsible for it. Bookings (€1,690) adds bookings on your own domain. Shop (€1,990 + €89/month) is a catalogue of up to 30 products. Operator (€3,950 + €99/month) is the largest package, for when the website is already part of the daily work. Care (€69/month) is maintenance: hosting, security patches and small content changes.
Here are the Web & eCommerce packages. We reply by email within 24 hours.
Frequently asked questions
How do I know whether an INCIBE alert affects my WordPress site?
Look at the “Recursos afectados” (affected resources) line in the alert, which names the product and the versions. Then open Tools > Site Health and go to the Info tab: according to the WordPress documentation, that is where active and inactive plugins are listed with their versions. If the name matches and your version falls within the range, it concerns you. If the plugin isn’t on your list, it doesn’t, even if the alert says critical.
Should I turn on automatic updates for plugins?
Since WordPress 5.5 they are switched on plugin by plugin on the Plugins screen. According to the documentation, WordPress runs them twice a day and, by default, sends an email when an update completes or fails. Before turning them on, the same documentation suggests making sure you can roll back to an earlier version using backups. Check, too, that those emails reach a business inbox that someone actually reads.
Who do I call if I think my site already has a problem?
INCIBE runs 017, its cybersecurity helpline. It is free and confidential, also serves businesses and professionals, and is open from 8 am to 11 pm, 365 days a year. You can call 017, message 900 116 117 on WhatsApp, find @INCIBE017 on Telegram or use the web form, which is answered by email.
