
A secure WordPress depends on four habits: update the core, plugins and themes straight away; have accounts with unique passwords and two-factor authentication; keep copies of the database and files outside the server, with the restoration tested; and choose hosting that keeps the server up to date and isolates accounts. 91% of the new vulnerabilities in 2025 were in plugins, according to Patchstack.
We should say where we have an interest: BDR Group is behind Hosting Andorra, which hosts WordPress websites. The advice applies with any provider, and what we say about Hosting Andorra comes from its public website, consulted on 25 October 2026.
Why updating matters
Patchstack, which publishes its own data, counted 11,334 new vulnerabilities in the WordPress ecosystem in 2025, 42% more than in 2024. 91% were in plugins, 9% in themes and only 6 in the core, of low priority. 46% had no fix from the developer when they were made public, and for the most exploited vulnerabilities the weighted median time to mass exploitation was 5 hours (report updated on 25 February 2026).
As for the core, version 7.1.3, of 6 October 2026, included seven security fixes, and 7.0.2, of 17 July, enabled forced updates for the affected sites, according to the official WordPress.org announcements.
Updates: core, plugins and themes
The official documentation (updated on 14 October 2026) explains what WordPress does by itself. Automatic updates have existed since version 3.7: minor core updates, which include security ones, are enabled by default on existing sites, and since 5.6 new installations also receive major ones. Plugin and theme updates are not automatic by default, except where the WordPress.org security team forces a critical fix; they can be enabled with filters. WordPress.org advises against disabling minor core updates.
Only the latest version of WordPress is officially supported; fixes to older versions are a courtesy. For that reason:
- Update the core, plugins and themes as soon as the fix is out, with a backup made beforehand.
- Remove the plugins and themes you do not use: the WordPress hardening guide recommends it.
- Check the PHP version: WordPress.org recommends PHP 8.3 or higher, and says that PHP 7.4 and MySQL 5.5.5 have reached end of life.
Accounts and two-factor authentication
The "Hardening WordPress" guide asks for strong, unique passwords and for two-step authentication to be enabled. It also recommends SFTP instead of FTP, HTTPS for administration, disabling the dashboard file editor with the DISALLOW_FILE_EDIT constant and not leaving the administrator user named "admin". It is also worth giving each person the minimum role they need: a content editor should not be an administrator.
Backups: what to keep, how often and where
The WordPress.org backup page asks you to keep the database and the files (core, themes, plugins, uploads, wp-config.php and .htaccess), as a single set made at the same moment. The frequency depends on activity: weekly for a small site and daily if it has a lot of activity, and always before an update. It recommends keeping between 3 and 5 recent copies, in different places and on different media. Automatic backups are valid, but it is worth making a manual one from time to time to confirm that the automatic one works.
In our view, what matters is the test: restore a copy in a separate environment and check that the site starts up.
Web application firewall (WAF)
A web application firewall filters traffic before it reaches WordPress. The hardening guide mentions it in three ways: a firewall plugin, a server-level WAF such as ModSecurity or a reverse proxy service. The WordPress security team also coordinates with the large hosting providers and with security companies on the deployment of fixes and of WAF mitigations.
A firewall reduces the risk while a vulnerability has no fix, but it does not replace updating: they are complementary measures.
Managed hosting: what to look at
WordPress.org asks you to choose a host that talks about its security, has stable and current server software, and offers reliable backups and recovery. It also recommends running PHP as the account’s user, not as the shared server user, and asking the provider about it.
As an example to read, according to the Hosting Andorra website its WordPress plans come with PHP 8.4 by default with PHP-FPM, a Let’s Encrypt SSL certificate that renews itself, the Plesk panel, Imunify360 protection of the whole server, accounts isolated from one another with CloudLinux CageFS, backups that you make and download from Plesk, and a data centre in Andorra. If you want the team to take care of WordPress and plugin updates, you can request maintenance with a quote.
With any provider, check in writing:
- Who carries out the core, plugin and theme updates, and how often.
- Where a copy is kept outside the server and who restores it.
- Which PHP version is offered and until when it will be maintained.
- Whether accounts are isolated and what protection against malware is in place.
- Through which channel and in which hours support is given.
In Andorra and Catalonia: if the website holds customer data
A website with forms, customer accounts or a shop processes personal data. Andorra’s Llei 29/2021 on personal data protection (Article 35) and the General Data Protection Regulation (GDPR, Article 32) require security measures appropriate to the risk, among others the ability to restore access to data quickly and a process to verify regularly that the measures work: a backup with a tested restoration fits this. If an attack exposes customer data, there is a 72-hour deadline to notify the authority (Article 36 of Llei 29/2021; Article 33 of the GDPR).
What to do now
- Make a full backup and test restoring it in a separate environment.
- Update the core, plugins and themes, and remove those you do not use.
- Enable two-factor authentication on the administration accounts and review the roles.
- Check the PHP version and what your hosting offers in firewall, isolation and backups.
- Decide who is in charge of the updates each month.
Frequently asked questions
Do I need a security plugin?
None is mandatory. The official hardening guide only suggests considering firewall plugins among other measures; in our view, what weighs most is updating, having well-protected accounts and backups that can be restored.
Is it worth enabling automatic plugin updates?
In our view, it can be reasonable for well-known plugins and with a recent backup, because it gains time against vulnerabilities exploited within hours. Major changes are tested first in a test environment.
Is WordPress-specific hosting worth it?
In our view, it depends on who does the maintenance: if the host or a technician updates, backs up and monitors, you save work and risk; if you do it yourself, you need a current server and access to the backups.
Sources
- Patchstack. State of WordPress Security in 2026 (2025 data; page updated on 25 February 2026). Accessed: 25 October 2026. https://patchstack.com/whitepaper/state-of-wordpress-security-in-2026/
- WordPress.org. Hardening WordPress. Developer documentation; updated on 14 October 2026. Accessed: 25 October 2026. https://developer.wordpress.org/advanced-administration/security/hardening/
- WordPress.org. Upgrading WordPress and background automatic updates; updated on 14 October 2026. Accessed: 25 October 2026. https://developer.wordpress.org/advanced-administration/upgrade/upgrading/
- WordPress.org. WordPress Backup Recommendations; modified on 14 October 2026. Accessed: 25 October 2026. https://developer.wordpress.org/advanced-administration/security/backup/
- WordPress.org. Security (supported versions and vulnerability management); modified on 24 April 2024. Accessed: 25 October 2026. https://wordpress.org/about/security/
- WordPress.org. Requirements (recommended PHP, MariaDB and MySQL); modified on 7 May 2026. Accessed: 25 October 2026. https://wordpress.org/about/requirements/
- WordPress.org. WordPress 7.1.3 Maintenance and Security Release, 6 October 2026, and WordPress 7.0.2 Release, 17 July 2026. Accessed: 25 October 2026. https://wordpress.org/news/2026/10/wordpress-7-1-3-maintenance-and-security-release/ and https://wordpress.org/news/2026/07/wordpress-7-0-2-release/
- General Council of Andorra. Llei 29/2021, del 28 d’octubre, qualificada de protecció de dades personals (Qualified Law 29/2021 of 28 October on personal data protection; in Catalan), Articles 35 and 36. BOPA no. 119, 17 November 2021. Accessed: 25 October 2026. https://www.apda.ad/assets/pdf/CGL20211115_08_58_32.pdf
- European Parliament and Council. Regulation (EU) 2016/679 (GDPR), Articles 32 and 33. OJ L 119, 4 May 2016. Accessed: 25 October 2026. https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32016R0679
- Hosting Andorra. WordPress websites in Andorra (public website). Accessed: 25 October 2026. https://www.hostingandorra.com/hosting-wordpress.php?language=english
Want to host or maintain your WordPress in Andorra?
You can see the WordPress plans, email and domains at Hosting Andorra. For web and digital strategy, see the Services section.



