Skip to content
CHOOSING YOUR APPROACH

Why Don't You Build Websites on WordPress?

Plugins, patches and attack surface: what the 2024 vulnerability data shows, what a static site removes and what still needs protecting.

By Brĭmeli · · Updated

DIRECT ANSWER

Because the risk in WordPress lives mostly in plugins, and our sites don't need them. Patchstack counted 7,966 new vulnerabilities in the WordPress ecosystem in 2024, 96% of them in plugins. We build static sites: pages built ahead of time and served as files, with no database or admin login on the public site for automated attacks to probe.

Key terms

Plugin
An add-on that extends a WordPress site with features such as forms, sliders or booking, written and maintained by a separate developer.
Attack surface
Every part of a website that an attacker can reach and try to exploit, such as login pages, databases and add-on code.
Static site
A website whose pages are built ahead of time and delivered as finished files, with no code running on the server when someone visits.

WordPress core isn't the weak point

WordPress itself is maintained by a large team and patched quickly. Patchstack found only seven vulnerabilities in WordPress core in all of 2024 [1]. The exposure comes from what gets added on top.

WordPress ecosystem vulnerabilities reported by Patchstack for 2024
Measure, 2024 Result
New vulnerabilities in the WordPress ecosystem 7,966, up 34% from 2023, about 22 a day
Share found in plugins 96%
Share found in themes 4%
Found in WordPress core 7
Exploitable without logging in 43%
Not fixed by the time they were made public 33%

All figures from Patchstack [1].

How attacks really arrive

Mass attacks are scripted. Scripts scan the web for sites running a known vulnerable plugin and try the same exploit on every one. Patchstack reports that in one 2024 case, mass exploitation began a few hours after the vulnerability was disclosed [1].

A typical business site on WordPress runs a dozen or more plugins. Each one depends on its developer patching quickly and on someone applying the update quickly. A third of the vulnerabilities in 2024 had no fix available when they were made public [1].

What a static site removes

A static site's pages are built before anyone visits and delivered as finished files from a global network. There is no database on the public site to break into, no login page to guess at and no plugin code running when a page loads. A scan looking for WordPress weaknesses finds nothing to work with.

It is also fast, for the same reason: the server hands over a finished page instead of assembling one on each visit.

What still needs protecting

A static site narrows the target. Some parts still need care:

  • The domain registrar account, which controls where the address points
  • The hosting and code repository accounts, which should use two-factor sign-in
  • Email for the domain
  • Forms, which need spam protection and a monitored destination
  • Any third-party script added to the pages

Who holds those accounts if the builder leaves is covered in what happens to your website if your developer disappears.

When WordPress is the right call

If your team publishes every day, wants to edit every page in a dashboard, or runs a feature that depends on plugins, such as a membership site, WordPress may suit you better, on a maintenance plan that applies updates every week. We aren't the right builder for that, and we will say so. Static site, CMS or website builder compares who edits what in each setup.

How Brĭmeli builds

We write each site in HTML, CSS and JavaScript, keep it in a code repository with every past version saved, test each change before release and deploy it to a global hosting network. Content changes go through the same review on our ongoing plans. See the website plans, or start a project if you want a site built this way.

Sources and method

The static and WordPress comparison and the guidance on when WordPress fits are Brĭmeli editorial judgments. The linked source supports only the statements numbered beside it. Source verified November 2, 2026.

  1. Patchstack: State of WordPress Security in 2025 (covering 2024)