Contact
EngineeringAug 9, 2026·22 min read

WordPress vs Headless CMS: What the Field Data Says and Which to Choose

KT
Keplaris TeamUpdated Nov 9, 2026
Illustration comparing an all-in-one CMS block with a headless content block feeding separate front ends

Choose traditional WordPress when one team runs one website and editors need to publish without developers. Choose a headless CMS when the same content must feed several front ends, such as a website and a mobile app, or when the front end is itself a product. Do not switch for speed. In HTTP Archive's Core Web Vitals data for September 2026, 48.3% of WordPress sites passed on mobile, against 35.7% of Next.js sites and 28.8% of Nuxt sites.

That last result runs against what most people expect, and against much of the marketing in this category. Many "WordPress vs headless CMS" comparisons are written by a company selling one side: a headless CMS vendor, a page-builder company, or an agency that builds one stack. The field data says architecture does not decide Core Web Vitals. Build discipline and hosting do. We build both, as a WordPress and custom web development studio, and this post makes the call on numbers we pulled from the primary sources on 9 November 2026.

An earlier version of this post, published in August 2026, used a third-party framework benchmark that put Next.js at 68% and Nuxt at 60%. HTTP Archive's own data does not reproduce those figures, so we replaced them and rewrote the conclusions that depended on them.

What Is the Difference Between WordPress and a Headless CMS?

Traditional WordPress is a monolith: content storage, the editorial interface and the public site are one PHP application. Your front end is a theme rendered by the same system that stores the content. That coupling is why it is productive (install, pick a theme, publish), and it is exactly what headless removes.

An API-first headless CMS, such as Contentful, Sanity, Storyblok or Strapi, is a content system built without a front end at all: it stores content, gives editors an interface, and serves the content over an API. Your public site becomes a separate application, usually built with Next.js, Nuxt or Astro, that you build, host and deploy yourself. Headless WordPress is a third option: WordPress with its theme layer replaced by a separate front end.

The core difference is this: WordPress renders pages itself, while a headless CMS only stores content and sends it over an API to a front end you build.

AspectTraditional WordPressHeadless (any CMS)
Editorial interfaceWordPress adminThe CMS's own editor (or WordPress admin, if headless WordPress)
Front endPHP theme, coupledYour own app, any framework
Content deliveryRendered pagesJSON over REST or GraphQL
Channels servedThe websiteAny number of front ends
Who ships a new pageAn editorAn editor for existing page types; a developer for new page types
What you operateOne systemCMS, front-end app and deploy pipeline

The last two rows are where projects succeed or fail, and we come back to them below.

WordPress Market Share and Headless Adoption: Numbers Worth Correcting

Start with the statistic many articles still open with: "WordPress powers 43% of the web." It is out of date. W3Techs put WordPress at 39.4% of all websites on 9 November 2026, which is 58.1% of the CMS market, down from 60.5% of the CMS market a year earlier.

The two measures tell different stories. WordPress's share of all websites held between 43.0% and 43.6% from January 2022 to January 2026, with the peak at 43.6% in January 2025. It then fell to 39.4% during 2026. Its share of the CMS market has been sliding for longer, every year since January 2022, when it stood at 65.2%.

Over the same period the gain showed up mostly in sites with no detectable CMS, not in rivals: between 1 January and 9 November 2026, sites with no detectable CMS rose from 28.6% to 32.3% of all websites, Shopify rose from 5.0% to 5.3%, and Wix stayed at 4.2%. WordPress still runs about seven times as much of the CMS market as Shopify (7.9%), its nearest competitor. A decline from dominance is not a death spiral, but if you are making a five-year platform bet, direction matters, and on both measures the direction is now down.

On the headless side, Grand View Research estimates the headless CMS software market at about $2.0 billion in 2026, growing 17.5% a year to 2033. Other firms' estimates vary widely, some at roughly twice that size, so treat any single figure as one firm's estimate. One adoption number deserves a flag: the widely quoted "64% of enterprises use headless" comes from a WP Engine study published in March 2021, based on 400 IT staff at companies with at least 1,000 employees. It is more than five years old and was commissioned by a company that sells headless WordPress hosting.

Is a Headless CMS Faster Than WordPress?

No, not by default. HTTP Archive's Core Web Vitals Technology Report joins Chrome's real-user data (CrUX, the field data behind Search Console's Core Web Vitals report) to the technologies it detects on each site. These are the mobile pass rates for September 2026, the latest month published when we pulled the data on 9 November 2026:

TechnologyMobile CWV pass rate, Sept 2026Sites measured
Wix80.9%177,709
Shopify76.2%445,297
Astro71.1%47,277
Squarespace71.0%89,052
All sites52.8%8,569,446
WordPress48.3%2,658,175
SvelteKit48.3%10,065
React43.9%1,283,019
Gatsby43.7%9,278
Vue.js36.2%609,131
Next.js35.7%395,345
Remix32.3%4,547
Nuxt28.8%93,276

Every row comes from the same request, run once per technology, with the pass rate computed from the "overall" metric:

GET https://cdn.httparchive.org/v1/cwv?technology=Next.js&geo=ALL&rank=ALL
pass rate = overall.mobile.good_number / overall.mobile.tested

2026-09-01  Next.js     140,984 / 395,345   = 35.7%
2026-09-01  WordPress 1,284,360 / 2,658,175 = 48.3%

The same method reproduces the 46.3% WordPress figure for November 2025 that this post cited in August, so the series is consistent. Two caveats apply. HTTP Archive counts a site toward every technology it detects there, so a WordPress site that also loads React counts in both rows. Eleventy (82.1%) is left out because only 195 sites were measured, and Angular is left out because its pass rate swung between 15.8% and 41.7% across the months we checked.

Three conclusions follow from the table:

  1. Framework choice does not buy a pass rate. The Next.js sites in the dataset passed less often than the WordPress sites, and the Nuxt sites less often still. Next.js improved from 29.7% in November 2025 to 35.7%, but it is still 12.6 points behind WordPress.
  2. The leaders are platforms that control the build and the hosting. Wix, Shopify and Squarespace decide the hosting, image pipeline and much of the front-end code for their customers. Astro ships static HTML with little JavaScript by default. In our reading, these sit at the top because fewer performance decisions are left to each team.
  3. Execution dominates architecture. Flexible stacks such as Next.js, Nuxt and WordPress leave hosting, images and third-party scripts to each team, and their pass rates land below the all-sites average. A disciplined WordPress build on good hosting, with a lean theme and an audited plugin list, can beat the typical headless site. So can a disciplined Next.js build.

Performance is a reason to go headless only when you need the ceiling (an Astro-style static front end, or Next.js done well) and have the engineering discipline to reach it. We reached the same conclusion for commerce in Headless Shopify with Hydrogen: Is It Worth It?: decoupling raises the ceiling and lowers the floor, and your team decides which one you get.

WordPress Security: 91% of Vulnerabilities Are in Plugins

"WordPress is insecure" is another claim this genre repeats often, and the data is more specific than the slogan. Patchstack's State of WordPress Security in 2026 (updated 25 February 2026) counted 11,334 new vulnerabilities in the WordPress ecosystem in 2025, up 42% on 2024. Of those, 91% were in plugins, 9% were in themes, and exactly six were in WordPress core. 46% had no patch from the developer by the time they were publicly disclosed.

So the accurate statement is: WordPress core is well-maintained; an unmanaged plugin stack is a liability. A WordPress site with eight audited, maintained plugins and a patch cadence is a very different risk from a site running thirty of them, three abandoned.

Headless changes the shape of the risk rather than deleting it. A decoupled front end shrinks the public attack surface: no PHP execution, no login page and no plugin endpoints on the public site, often nothing but static assets and an API. But the editorial backend still exists somewhere. Headless WordPress still runs wp-admin, just not on your public domain, and an API-first CMS moves the concern to vendor security, API tokens and the access-control logic you write yourself. Going headless means trading a patching discipline for a secrets-and-permissions discipline. Teams that lacked the first rarely have the second by accident.

WordPress Security Hardening, and What Headless Changes

WordPress security hardening means reducing a site's attack surface and its patch lag: fewer and better-maintained plugins, prompt updates, strong admin authentication, tight file and database permissions, and limited exposure of admin and API endpoints. Updates alone are not enough when, per Patchstack, 46% of 2025's vulnerabilities had no patch at disclosure. The controls below come from WordPress.org's Hardening WordPress guide (last modified 14 October 2026), except where another source is named.

ControlWhat it preventsHow
Keep core, plugins and themes updatedExploits of known, patched flawsRun the latest release; WordPress has offered automatic updates since version 3.7
Delete unused plugins and vet new onesAbandoned or malicious codeDelete any plugin you do not use, avoid untrusted sources, read the code of plugins that ask for write access, and avoid plugins that execute code
File permissionsOther processes changing your filesDirectories 755, files 644, wp-config.php 400 or 440
Disable the dashboard file editorA stolen admin login becoming PHP editsAdd define( 'DISALLOW_FILE_EDIT', true ); to wp-config.php. The guide notes it does not stop malicious uploads
Two-step authenticationStolen or guessed passwordsTurn it on for every account that can log in to wp-admin
Protect wp-adminBrute-force attempts and exposed admin pagesAdd server-side password protection such as BasicAuth to /wp-admin/ (it can break the AJAX handler), and require HTTPS for admin
Least-privilege database userAn injection flaw escalatingThe guide says normal operation needs only SELECT, INSERT, UPDATE and DELETE, but it does not recommend revoking the rest, because updates that change the schema can fail. If you do it anyway, keep tested whole-database backups first
Web application firewallCommon exploit trafficPlugin level (Wordfence, Shield), server level (ModSecurity), or a reverse proxy (Cloudflare, Sucuri)
BackupsData loss and a slow recovery after a compromiseBack up regularly, include the database, and protect backup integrity with encryption, checksums or read-only media
XML-RPCAttacks through xmlrpc.phpNot covered by WordPress.org's guide. Pantheon's documentation recommends against XML-RPC and explains how to re-enable it for tools that need it, such as Jetpack or the WordPress mobile app. Block it only if nothing you use depends on it

One thing the guide does not recommend is rotating your security keys and salts on a schedule. Its only reference on the subject is an article titled "How WordPress Uses Salts and Why You Should Not Rotate Them".

Hardening a headless WordPress backend

Headless removes the public login page, not the login page. Everything in the table still applies to the WordPress install behind your front end, and the API adds its own surface:

  • The WordPress REST API is public by default. The users endpoint returns each published author's ID, display name and slug to anyone, and by default the slug is derived from the login name. If your front end does not need it, block the endpoint for unauthenticated requests.
  • WPGraphQL ships some limits and leaves others to you. Per its security docs, public schema introspection is off by default, but debug mode lets logged-out visitors read the schema, so keep debug mode off in production. New installs limit query depth to 15 levels; sites that installed WPGraphQL before that default keep their old setting, which is off unless someone turned it on. Depth limits do not cap how wide a query is, so also keep the per-page connection cap (100 items by default) and limit or disable batch queries in the plugin's settings.
  • Scope the tokens your front end uses. Server-side fetches can authenticate with an Authorization header, for example an application password. An application password carries the capabilities of the user it belongs to, so create a dedicated user with the lowest role that can read what the front end needs, and keep the secret on the server, never in browser code.
  • Keep wp-admin off the public domain. Put the backend on its own hostname behind the access controls in the table above.

What a Headless CMS Costs Beyond the Subscription

WordPress software is free under the GPL, while API-first headless CMSs charge subscriptions that scale with seats and features. Vendor list prices are in the CMS comparison table below. This table covers the cost lines beyond the licence:

Cost lineTraditional WordPressAPI-first headless
Software licenceFree (GPL)Subscription by seat or tier; see the CMS table below
Enterprise featuresMostly plugin-pricedSSO is in the top, custom-priced tier at Sanity and Storyblok
HostingOne managed WordPress hostFront-end hosting (for example Vercel or Netlify), plus the CMS, usually SaaS
Forms, redirects, SEO meta, sitemaps, searchPlugins, mostly freeEngineering work, per feature
Draft preview in contextBuilt inAn engineered pipeline
Contract riskHosting-levelVendor-level: Vendr's marketplace data puts the median Contentful enterprise contract at about $54,000 a year, with a range of roughly $24,000 to $128,000 (Sengo, October 2026)

A rough rule of thumb, not measured data: a marketing site that is a four-to-six-week WordPress build tends to become an eight-to-fourteen-week build as a decoupled stack, call it 1.5 to 3 times the initial cost, because most of what the plugin ecosystem provides gets rebuilt as code. That premium buys real things: a front end with no inherited constraints, one content source for many channels, and independence from the plugin supply chain. It is only worth paying if you will use one of those. "Our site will feel more modern" is not one of them, and the Core Web Vitals table above shows that speed is not guaranteed either.

There is a second-order cost worth naming: editorial autonomy. In WordPress, a marketer ships a landing page on a Tuesday afternoon. In most headless setups, new page types, and sometimes new pages at all, go through an engineering ticket. Some teams buy that back with visual editing tools (Storyblok's visual editor, Sanity's Presentation tool), but it is bought back with configuration work, not installed.

Platform Risk: WordPress Governance and Vendor Pricing

Both WordPress and SaaS headless CMSs carry platform risk: WordPress through an unresolved legal dispute over who controls its infrastructure, and SaaS vendors through pricing power.

On the WordPress side, the Automattic and WP Engine conflict that began in September 2024 was still in litigation in November 2026. WP Engine's third amended complaint (February 2026) alleges that Automattic planned to seek trademark royalties from ten hosting companies; Automattic told TechCrunch: "There is nothing new here." On 24 September 2026, Judge Araceli Martínez-Olguín of the Northern District of California revived WP Engine's monopolization and tying claims and found that Automattic and Matt Mullenweg are "neither owners nor registrants of the marks at issue", because the marks belong to the WordPress Foundation, whose counterclaims continue, as webhosting.today reported on 29 September 2026. The same report puts a jury trial in October 2027. Separately, a proposed class action on behalf of WP Engine customers was filed in February 2025.

The structural fact underneath: WordPress.org, the update and plugin-distribution service the ecosystem depends on, is personally controlled by one person, Matt Mullenweg. The 2024 episode in which WP Engine's customers lost access to plugin updates through WordPress.org showed what that means in practice. A December 2024 preliminary injunction ordered access restored, and the ecosystem kept working. The risk is real but has so far been contained.

On the headless side, the risk is commercial: your content infrastructure is a SaaS vendor with pricing power. Enterprise contract sizes like those in the cost table, per-seat models that grow with your team, and SSO reserved for top tiers are the observable pattern. The mitigations have costs of their own. Open-source or source-available headless CMSs (Strapi, Payload, Directus) trade the subscription for self-hosting work, and API-first content is more portable on the way out than a themed WordPress database, an underrated long-term advantage of the headless model.

Neither risk is disqualifying. Both belong in the decision.

The False Binary: Headless WordPress

Headless WordPress is a third option: the WordPress admin manages content, and a separate front end such as Next.js displays it. It exists because "WordPress vs headless CMS" is really two independent decisions:

  1. Which editorial backend? WordPress, or an API-first CMS (Contentful, Sanity, Storyblok, Strapi and others)
  2. Coupled or decoupled delivery? A theme rendered by the CMS, or your own front end consuming an API

All four combinations exist. Headless WordPress fits teams whose editors know and like WordPress but whose product needs a custom front end. The price is operating both stacks and rebuilding conveniences such as preview, menus and redirects that coupled WordPress includes. We built and tested one locally against a replay of the WordPress REST API, with the caching, revalidation and outage behaviour measured, in Headless WordPress with Next.js.

The coupled quadrant has not stood still either. WordPress 6.9 "Gene" (December 2025) added block-level Notes for editorial comments and the Abilities API. WordPress 7.0 "Armstrong", released on 20 May 2026, added an AI Client in core for connecting to generative AI models, a visual way to scrub through and restore revisions, and new Gallery, Heading, Breadcrumbs and Icons blocks. WordPress 7.1 "Mary Lou" followed on 19 August 2026, and the current release is 7.1.4. The "WordPress editing is stuck in 2015" argument that drove early headless migrations no longer holds.

Sanity vs Contentful vs Storyblok vs Strapi vs WordPress: Choosing the CMS

Choosing the CMS means picking who hosts it, how editors work in it, and how its price grows with your team. The main API-first options split into SaaS products (Contentful, Sanity, Storyblok) and open-source products you can host yourself (Strapi). WordPress can be either coupled or headless. Every Contentful, Sanity, Storyblok and Strapi cell comes from that vendor's own pricing page, read on 9 November 2026. The table is in alphabetical order and is not a ranking.

CriterionContentfulSanityStoryblokStrapi (self-hosted, Cloud)WordPress
Hosting modelPage did not loadContent stored in Sanity's hosted Content Lake; Studio editor hosting includedHosted by StoryblokSelf-host, or Strapi Cloud per projectSelf-host or any WordPress host
LicencePage did not loadStudio is open source; Content Lake is Sanity's proprietary hosted service, free up to plan limits and paid above themSubscriptionOpen source (MIT), per its pricing pageGPL
Entry pricePage did not loadFree up to 20 seats; Growth $15 per seat a month, up to 50 seatsFree Starter (1 seat); Growth $99 a month with 5 seats, extra seats $15, maximum 10; Growth Plus $349 with 15 seatsCommunity free; Growth $45 a month with 3 users, extra users $15; Cloud from $35 a month per projectFree software; you pay for hosting
Visual editingPage did not loadVisual editing and Presentation tool on all plansVisual editor on all plansLive Preview on Growth and EnterpriseBlock editor (coupled sites only)
PreviewPage did not loadLive Preview on all plans2 preview URLs on Starter, 6 on Growth and Growth PlusLive Preview on Growth and EnterpriseBuilt in when coupled; engineered when headless
SSOPage did not loadEnterprise only (custom price)Premium and Elite only (custom price)Growth add-on at $150 a month plus $50 per user; included in EnterpriseNot in core; plugins
Fits whenCheck its pricing page yourself before shortlistingDevelopers want to configure the editor in code and editors need in-context previewMarketers want a visual page editor and the team fits in 15 seatsYou want to self-host and own the databaseEditors already know WordPress, or you want plugins and built-in preview

Contentful's pricing page returned HTTP 429 (too many requests) on every attempt that day, so we have left its cells empty rather than repeat third-party figures.

Monthly software cost at three team sizes, from the list prices above (list price arithmetic, not quotes; excludes hosting, overages and taxes):

EditorsSanityStoryblokStrapi self-hostedWordPress
3$0 on Free, or $45 on Growth$99 (Growth)$0 on Community, or $45 on Growth$0
10$0 on Free, or $150 on Growth$174 (Growth, 5 extra seats at $15)$0 on Community, or $150 on Growth (7 extra users at $15)$0
25$375 (Growth; Free stops at 20 seats)Custom (above Growth Plus's 15 seats)$0 on Community, or $375 on Growth (22 extra users at $15)$0

SSO is excluded from every priced cell. Adding it means Sanity Enterprise or Storyblok Premium, both custom-priced, or $150 a month plus $50 per user on Strapi Growth.

When to Choose WordPress vs a Headless CMS

Choose WordPress for one website run by editors, headless WordPress when editors know WordPress but the front end is a product, and an API-first headless CMS when content feeds several channels. The choice comes down to three questions: how many channels the content feeds, whether editors must publish without developers, and whether the front end is a custom product.

Your situationChooseMain cost you accept
One team, one website, editors publish without developersTraditional WordPressPlugin patching discipline
Editors know WordPress, but the front end is a custom productHeadless WordPressRunning two stacks, rebuilding preview and redirects
Content feeds web, app and other channels from one sourceAPI-first headless CMSA build premium we estimate at 1.5 to 3 times, plus seat or tier pricing
The only goal is a faster siteNeither; fix hosting, images and scriptsThe optimization work itself

Choose traditional WordPress when one team runs one website, editors must be self-sufficient, the budget suits a four-to-six-week build, and your performance target is a fast, well-built site rather than an Astro-level pass rate. Discipline (lean theme, audited plugins, managed hosting, patch cadence) matters more than architecture. If the theme is the open question, our custom theme vs page builder comparison measures what each option adds to page weight and Core Web Vitals. This is still the right answer for most marketing sites, content businesses, and local and B2B sites, which is part of why WordPress still runs about two-fifths of the web.

Choose headless WordPress when your editorial team is WordPress-native but the front end is a product: custom interactivity, an app-like experience, components shared with a SaaS product, or a design system that WordPress theming would fight. You accept two stacks in exchange for keeping the editorial workflow your team already knows.

Choose an API-first headless CMS when content feeds several channels (web, mobile app, in-product and partners), when structured content modelling is central to the product, or when an engineering-led team is building front end first and the CMS is one API among several. Budget for a build premium we estimate at 1.5 to 3 times, the subscription at your real team size, and a clear answer to "how do editors preview a draft?" before you sign.

Don't migrate at all when the motivation is performance alone. The field data points the same way: execution decides more than architecture does. Fix hosting, images and scripts first, on whichever architecture you have, before paying for a migration.

One note applies to every option. In Vercel's December 2024 analysis of AI crawler traffic, none of the major AI crawlers it studied, including OpenAI's and Anthropic's, rendered JavaScript; Google's Gemini, which uses Googlebot's infrastructure, and AppleBot were the exceptions. Content that appears only after client-side rendering is invisible to those crawlers. That is one more reason a decoupled front end must render on the server or at build time. Coupled WordPress serves HTML by default.

How We Decide at Keplaris

We build both WordPress and custom web stacks, which is why this post does not end in a sales pitch for either. Our WordPress builds ship with hardened security, a locked-down admin, a minimal plugin footprint, version-controlled code, staging environments and automated backups. On a headless build, the same discipline moves to the API, the tokens and the front-end deploy.

If you are weighing a replatform (WordPress feeling slow, a headless quote feeling expensive, or an agency telling you the architecture is the problem when the field data above suggests execution is), talk to us.

Frequently asked questions

Is a headless CMS better than WordPress?

Neither is better in general; they optimize for different things. WordPress is better when one team runs one website and needs to ship content without engineering involvement: it is cheaper to build, editors are self-sufficient, and plugins cover most requirements. A headless CMS is better when the same content must feed several front ends, such as a website and a mobile app, or when the front end is itself a custom product. Do not decide on speed: in HTTP Archive's September 2026 field data, the WordPress sites measured passed Core Web Vitals more often than the Next.js sites measured.

Is a headless CMS faster than WordPress?

Not by default. In HTTP Archive's Core Web Vitals Technology Report for September 2026, 48.3% of WordPress sites passed Core Web Vitals on mobile, against 35.7% of Next.js sites and 28.8% of Nuxt sites. Astro sites passed at 71.1%. Architecture does not decide the result; build discipline and hosting do. A well-built headless front end can be very fast, and so can a lean WordPress theme on good hosting.

Can WordPress be used as a headless CMS?

Yes. Headless WordPress keeps the WordPress admin as the editorial backend and serves content over the WordPress REST API or WPGraphQL to a separate front end, usually Next.js. WP Engine's Faust.js toolkit adds helpers for routing, authentication and previews, and its README documents the Next.js Pages Router. Editors keep the interface they know. The cost is running two systems: you host and secure WordPress, run a front-end deployment, and build features such as draft preview that coupled WordPress gives you for free.

What are the disadvantages of a headless CMS?

Four show up in practice. First, build cost: in our estimate, a headless build costs 1.5 to 3 times an equivalent WordPress build, because forms, redirects, SEO metadata, sitemaps and preview become engineering work. Second, editorial dependence: marketers cannot install a plugin or add a page type without a developer. Third, subscriptions: on 9 November 2026 Storyblok listed Growth at $99 a month and Growth Plus at $349, Sanity listed Growth at $15 per seat, and SSO sat in the top, custom-priced tier at both. Fourth, preview: seeing a draft in context is built into WordPress and an engineered feature in a decoupled stack.

Is WordPress dying?

No, but it is shrinking. W3Techs put WordPress at 39.4% of all websites and 58.1% of the CMS market on 9 November 2026. That is still about seven times Shopify, its nearest rival, but its share of the CMS market has fallen every year since January 2022, and its share of all websites dropped from 43.0% to 39.4% during 2026. Over the same months, the share of sites with no detectable CMS rose by about as much, while Shopify and Wix barely moved. The Automattic and WP Engine litigation was also still unresolved in November 2026.

Which is the best CMS: Sanity, Contentful, Storyblok, Strapi or WordPress?

There is no single best CMS; the right one depends on who edits, who hosts and how many channels you serve. WordPress fits teams whose editors already use it and want plugins and built-in preview. Storyblok fits marketers who want a visual page editor on a small team. Sanity fits developers who want to configure the editor in code, with a free tier up to 20 seats. Strapi fits teams that want to self-host the CMS and own the database. Check Contentful's current pricing page yourself; it did not load when we checked on 9 November 2026.

How do you harden WordPress security?

Start with plugins, because Patchstack found 91% of the 11,334 new WordPress vulnerabilities in 2025 in plugins. WordPress.org's Hardening WordPress guide then recommends keeping everything updated, deleting unused plugins, setting directories to 755 and files to 644, disabling the dashboard file editor with DISALLOW_FILE_EDIT, turning on two-step authentication, protecting wp-admin, adding a firewall and keeping regular backups; it explains how to restrict the database user but does not recommend it by default, because updates that change the schema can fail. On headless WordPress, also lock down the REST API and WPGraphQL endpoints.

Next articleShopify Conversion Rate Optimization: A Practical Playbook

Get in touch.

Whether you have questions or just want to explore what's possible, we're here to help.