WordPress Plugin Exploitation in Late 2026: Why the Theme Is Never the Problem
Attackers moved on Bricksforge within days of disclosure, uploading and executing PHP on unpatched sites. The pattern behind that campaign is the same one that takes most Omani business websites down, and it has very little to do with WordPress itself.

What happened with Bricksforge
Bricksforge, an add-on for the Bricks page builder, carried a vulnerability tracked as CVE-2026-85097 with a CVSS score of 9.8. It allowed unauthenticated attackers to upload and execute arbitrary PHP code — in practice, full control of the site and the account it runs under. Patchstack began observing exploitation attempts in the wild on 7 October 2026. The flaw is fixed in version 3.1.8.10; everything up to and including 3.1.8.9 is affected. It was not alone in the period. Everest Forms (CVE-2026-19598) exposed more than 100,000 sites to takeover, Forminator Forms (CVE-2026-15748) was disclosed without reports of exploitation at the time, and Modular DS (CVE-2026-23550) was reported as actively exploited for unauthenticated admin access.
The pattern, which matters more than any single CVE
Four observations are worth more than the individual advisories. **It is almost never WordPress core.** Core has a mature security process and a responsive team. The exposure lives in the plugin layer, where quality varies from professional to abandoned and where a single site may carry twenty-five of them. **Form and builder plugins recur.** Look at the list: Bricksforge, Everest Forms, Forminator. This is not coincidence. These plugins exist to accept input from people who are not logged in, and file upload is a feature they are expected to provide. That is the most dangerous combination in web security — untrusted input, a write to disk, and a server that executes PHP from disk. **The window has collapsed.** Exploitation of Bricksforge began within days of disclosure. Internet-wide scanning for a newly published WordPress CVE is now automated and immediate, so "we patch monthly" is a strategy built for a threat model that no longer exists. **The entry point is rarely the target.** A compromised brochure site is useful as a phishing host, a spam relay, a crypto-miner, or a staging post into whatever else shares that server or those credentials. "It is only our marketing site" describes the value of the content, not the value of the access.
Why this bites harder in Oman than the raw numbers suggest
Many Omani organisations run their public website on WordPress while the real business systems sit elsewhere. That split creates a governance gap: the website is often owned by marketing, hosted on whatever was cheapest, built by whoever ran the last campaign, and not covered by the IT department's patch process. Nobody is formally responsible for its plugin inventory. There is also a compliance dimension that is easy to miss. If a site collects enquiries, CVs or appointment bookings, it processes personal data, and Oman's Personal Data Protection Law applies to that data regardless of which department considers the site theirs. A compromised contact form is a personal data breach, not a marketing inconvenience.
What actually works
**Inventory before patching.** You cannot patch what nobody has listed. Every plugin, its version, whether it is still maintained, and who decided to install it. Most sites we assess carry plugins nobody can account for. **Remove more than you update.** The fastest way to reduce this attack surface is to delete plugins that are deactivated, duplicated, or abandoned upstream. A deactivated plugin still has files on disk, and some vulnerabilities are reachable without activation. An abandoned plugin will never be patched, so no update policy protects you — only removal does. **Automate updates, with a safety net.** Enable automatic updates for plugins and core, but pair them with staging and backups, because the reason teams disable auto-updates is a past update that broke the site. Solve that with a rollback path rather than by turning off patching. **Restrict execution in upload paths.** If PHP cannot execute from the uploads directory, an arbitrary file upload becomes a storage nuisance instead of a shell. This is a web server configuration change that blunts an entire vulnerability class, including the Bricksforge case. **Monitor for the aftermath.** File integrity monitoring and outbound connection alerts are what tell you about a compromise that happened before the patch landed. Patching closes the door; it does not tell you who is already inside.
A fair question: should you still use WordPress?
Often, yes. For a content-led marketing site with non-technical editors, WordPress is a reasonable choice and the alternative is rarely better maintained. The problem is not WordPress — it is running WordPress with twenty-five unaudited plugins and no owner. But if the site has grown into something that handles customer data, authenticates users, or integrates with core business systems, the plugin model stops being a convenience and becomes the main risk. At that point a purpose-built application with a controlled dependency set is usually the cheaper option over any reasonable horizon, because the ongoing exposure stops scaling with the number of third-party plugins installed.
How IIT Oman can help
We handle both sides of this. For sites staying on WordPress, we run plugin and vulnerability audits, remove the surface nobody needed, configure upload-path hardening and automatic updates with a tested rollback path, and put monitoring in place so you learn about a compromise from your own alerting rather than from a customer. Where a site has been compromised, our cybersecurity practice — led by internationally credentialed investigators — performs incident response and digital forensics to establish what was accessed, which matters for Oman PDPL notification obligations as much as for cleanup. And where WordPress has been outgrown, our engineering team builds bespoke platforms with a controlled dependency set and bilingual Arabic and English interfaces, migrating content without losing the search visibility already earned. If nobody in your organisation can currently name every plugin on your website, that is the finding. Talk to our team in Muscat and we will produce the list.

