WordPress Security: How Well Is Your Website Protected Against AI Attacks?

Two critical PHP vulnerabilities in October, a bypassable password check in Alpine Linux in November: even basic server components can contain flaws. At the same time, attackers are using AI to research vulnerabilities and prepare attacks. If you build your website with AI or run WordPress yourself, you face a concrete question: how can you check your own WordPress security, and what does the result actually tell you?1,2,3
A WordPress security check from the outside can uncover vulnerabilities. Whether users can reach other people's data, misuse paid features or get in via the server needs additional checks. What matters is that access rules really hold, security updates are installed and every finding is backed up with evidence. A convincingly worded AI report alone is not enough.
What the PHP and Alpine cases mean for website owners
On 21 October 2026, the PHP team released security updates for two critical flaws. Under the relevant conditions, attackers could run their own code on affected systems without logging in first. PHP is the runtime environment that, among other things, WordPress runs on.1
On 5 November, Alpine Linux warned about a different vulnerability. In certain configurations, the password check of SSH, the remote access service for servers, could be bypassed. Affected were systems with password login enabled and further conditions. A WordPress login in the browser was not what this was about.2
Both reports show why a look at the visible website is not enough. A site can work normally while software that needs a security update is running underneath. However, these cases prove neither an AI attack nor that your own website is affected. For that, you need to check which components and settings you are actually using.
What changes when attackers use AI
AI doesn't only help with building a website. Google's Threat Intelligence Group also describes its use by attackers, for example in researching vulnerabilities and developing malware. That gives them extra support for such tasks.3
An attacker doesn't have to stick with a chatbot that refuses their request. There are modified models whose refusal behaviour has been reduced. One example is a modified DeepSeek variant that Morph offers as “abliterated”. Here, the model itself was edited to reduce its refusal behaviour.4,5
That doesn't make DeepSeek as a whole an AI without guardrails. Nor does it say anything about how reliably the modified variant finds security vulnerabilities. For your own protection, though, the point still matters: the security of a website must not depend on whether an attacker's model answers a question. The application has to prevent unauthorised access itself.
Can someone cause damage through your website?
Yes, if a reachable function contains an exploitable vulnerability. A visitor is not limited to the buttons your interface shows. The interfaces behind it can also be addressed directly. Two examples show what is at stake.
Other people's invoices despite a correct login
Anna logs in to a customer portal and opens her invoice. If she can also retrieve Bernd's invoice, the server did recognise her login but did not sufficiently check her permission for that invoice. The fact that Bernd's invoice doesn't appear in Anna's overview doesn't fix the flaw.
The technical term for this is IDOR, meaning insufficiently protected access to a specific data object. For site owners, the key point is what needs testing: in your own test environment, separate accounts must show that everyone gets their own intended data and can neither read nor change other people's private data. OWASP recommends checking permissions on every request.6
Using an AI feature at your expense
If your website analyses images or generates text and you pay the provider per call, uncontrolled use can cause costs. A visible counter of remaining uses in the browser is not enough as a safeguard. The limit has to take effect on the server, before the paid call starts.
You should also check whether the limit holds up under simultaneous requests and what stops the total spend across all users. A limit per minute is not yet a monthly budget. OWASP lists missing limits on resources and spending as an API security risk in its own right.7
What an external WordPress security check detects
An external test can, for example, examine publicly visible settings, HTTPS and security headers. Headers are additional information in the server's response that can be used, among other things, to pass protection rules to the browser. Checks like these are a sensible starting point.
However, they don't automatically answer the invoice question, the cost question or the security status of the whole server environment. For that you need suitable access, targeted functional tests and, where appropriate, a review of code and configuration.
If an AI agent carries out the checks, the final verdict isn't enough for me. I want to see which address was checked, which tool ran successfully and which response supports the finding. If a tool fails or an area is skipped, that has to remain visible in the report. A convincing-sounding explanation doesn't replace a check that wasn't done.
Securing WordPress: which checks belong together
A useful security check looks at several layers. The following overview helps you gauge the scope of a report.
| Area | What should be checked | What this does not yet prove |
|---|---|---|
| WordPress, plugins and themes | Compare installed components against known vulnerabilities | That no unknown vulnerabilities exist |
| Files | Compare against original references and assess suspicious changes | That every deviation is malware |
| Users and functions | Check access with separate test accounts and appropriate roles | That every conceivable workflow is covered |
| Paid services | Test server-side limits and the overall budget | That a counter in the browser effectively limits usage |
| Server | Check the services, settings and package versions actually in use | That the visible version number alone proves a vulnerability |
| Recovery | Restore files and database in a separate environment | That a successful backup message confirms the restore |
Published checksums exist for WordPress files and for plugins from the official directory. A deviation first shows only that a file doesn't match the reference used. Whether a customisation, damage or unauthorised interference is behind it has to be clarified afterwards.8
It's also worth looking more closely at server versions. The website may use a different PHP installation than the command line. In addition, vendors sometimes ship security fixes as backports into existing package versions. So for my assessment, I need the service actually in use and the security information from the package vendor.9 With self-hosting, it has to be clear whether you or a commissioned administrator will handle this check and the maintenance that follows.
What our own practical test showed
For the Simon Traffic WordPress security check, inventory data, vulnerability comparisons, file checks and server reports were brought together. This also showed how important it is to verify individual alerts.
In the first real static scan, two PNG images were flagged. The compressed image data happened to contain short character strings that resembled PHP code. The targeted check identified these markers as false alarms. A common empty protective file had also initially been flagged for review.
The detection rules were then made more precise and tested with real-world samples and counterexamples. None of these files was deleted or changed for this. The case shows that a suspicion needs an assessment before it turns into a repair measure.
A helpful report therefore distinguishes three states: a confirmed problem, an unresolved suspicion and an area that was not checked. Each leads to different next steps. This distinction helps the site owner more than a long list of warnings that all look alike.
Are Cloudflare and a security plugin enough?
Cloudflare can filter the traffic passing through it according to rules and provide additional protective features. Which features are available depends on the setup and the plan.10 A security plugin can take on further checking or protection tasks.
Whether Anna may read Bernd's invoice is still something the application has to decide. Server updates, cost limits and recovery also remain separate tasks. For each of these areas, it should be clear who looks after it and what evidence exists.
As for backups, a typical WordPress restore needs both files and database together. Whether your own process works can be tested with a restore in a separate test environment.11
How to assess your own security better
You don't have to be able to run every check yourself. But a report should enable you to ask the right follow-up questions:
- What was checked? With the date, the scope and any areas explicitly left out.
- What is actually proven? With a traceable source or a concrete test result.
- What has to happen first? With a reason that relates to your website.
- Who takes care of the measure? With clear responsibility and a concrete next step.
- How will success be verified? With a retest that examines the original flaw again.
For customer data, payments and complex user permissions, I would plan for expert support. That is exactly where a general all-clear isn't enough. The important workflows have to be tested specifically.
When attackers use AI, what matters for site owners is still that the technical boundaries really hold. A traceable security check shows where that was verified, where action is needed and which questions are still open. On that basis, you can decide what is needed next, and that is what good WordPress security comes down to.
Frequently asked questions about WordPress security
Answers to questions that website owners also ask in public Reddit discussions.15
Is WordPress secure enough for beginners and small websites?
Even a small WordPress website needs up-to-date software, secure access and working backups. What matters is that these tasks get done. You don't have to be able to do everything yourself; for server maintenance and sensitive features, a suitable hosting provider or expert support can help. A small number of pages is not proof of security on its own.12
Are free Wordfence and Cloudflare enough to secure WordPress?
Wordfence Free already includes a firewall, a scanner and login protection. According to the vendor, the free version receives new firewall rules and malware signatures 30 days after Premium.13 Cloudflare can additionally filter the incoming traffic passing through it.10 Whether the free combination is enough for your website depends on the specific risk and the setup. Even with a paid version, updates, access rights and custom features still need to be checked.12
How can I check the security of my WordPress website?
Start with an inventory of WordPress, plugins, themes and the server environment actually in use. Next come a comparison against known vulnerabilities, a file check and tests of the important functions with appropriate user roles. Record the result, date and open areas for each step. The overview further up shows which questions belong to which check.
If I suspect malware, do I also have to check the WordPress database?
Yes, an investigation can cover database contents, accounts and configuration as well as files. A file scan alone doesn't catch every possible manipulation. So don't delete unknown database entries on suspicion: secure the findings and have the affected areas assessed specifically.14
WordPress hacked – what should I do first?
Document anything unusual and when it happened, secure any existing logs and bring in your host or expert help. Active malicious content must not keep putting visitors at risk. Before restoring, you need a verified clean state; the cause and the affected access also have to be dealt with. An update alone does not prove a clean-up.14
How do I restore a WordPress backup without bringing the infection back?
First check a backup that is likely to be clean in a separate environment. For a typical restore, you need files and database that match each other. Before going back live, the original point of entry and any compromised access must have been dealt with. If the timing or extent of the infection is unclear, have the backup checked by an expert.11,14
Sources
- PHP team (21/10/2026): Security advisory: Critical remote code execution vulnerabilities, update now. php.net.
- Alpine Linux (05/11/2026): Security advisory: openssh-server password authentication bypass. alpinelinux.org.
- Google Threat Intelligence Group (05/11/2025): GTIG AI Threat Tracker: Advances in Threat Actor Usage of AI Tools. cloud.google.com.
- Morph: Open Source Models, section DeepSeek Uncensored. Vendor description, retrieved on 11/11/2026. docs.morphllm.com.
- Arditi et al. (2024): Refusal in Language Models Is Mediated by a Single Direction. arxiv.org.
- OWASP: Authorization Cheat Sheet. cheatsheetseries.owasp.org.
- OWASP (2023): API4: Unrestricted Resource Consumption. api-security.owasp.org.
- WordPress Developer Resources: Checksum verification for WordPress core and plugins.
- Canonical: Security updates, Ubuntu security documentation. documentation.ubuntu.com.
- Cloudflare: Web Application Firewall, how it works and availability by plan. developers.cloudflare.com.
- WordPress Developer Resources: Backups. developer.wordpress.org.
- WordPress Developer Resources: Hardening WordPress. developer.wordpress.org.
- Wordfence: Scan and Wordfence Free, vendor descriptions. Scan, Wordfence Free.
- WordPress.org: FAQ My site was hacked. wordpress.org.
- Reddit r/Wordpress, as sources for the user questions, not as technical proof of security: Security for beginners, 30/10/2026, Wordfence Free and Cloudflare, 04/05/2026, Recovery after malware, 21/04/2026. For the last post, the original text is preserved in the public Reddit archive; the Reddit page now shows it as removed.
The experience with the image files comes from our own Simon Traffic project. It is not proof that a site is completely free of malware. Sources last checked on 11/11/2026.
Simon Gütter is a marketing expert and has worked for years at the intersection of marketing, sales and automation. He finds the places where companies lose time and customers, and builds workflows that run by themselves: from appointment booking to reporting. More about Simon