Headless WordPress + Nuxt

Hit by wp2shell or PHP2Shell? Take WordPress off the internet.

We rebuild your website as a fast Nuxt frontend on Cloudflare’s edge, and move your WordPress CMS behind a private, access-controlled door. Your editors keep the tools they know. Attackers lose the target.

access.log — live
  1. 03:12:44POST /wp-admin/admin-ajax.php — 200
  2. 03:12:45new file: wp-content/uploads/2026/07/cache.php
  3. 03:12:51plugin activated: wp-optimise-core (unknown)
  4. 03:13:02user created: support_admin (administrator)
  5. 03:13:30outbound connection → 185.xx.xx.12:443
  6. 03:14:08homepage defaced · SEO spam injected
A typical compromise timeline: webshell, rogue plugin and hidden admin account in under two minutes.

01 The problem

Patching is a race. You don’t have to run it.

WordPress core

wp2shell

A remote code execution chain in WordPress core, actively exploited to install malicious plugins and drop webshells onto public sites.

Patching closed this hole. But every public wp-admin, plugin and PHP endpoint is still a door waiting for the next one.

PHP runtime

PHP2Shell

Critical vulnerabilities in the PHP language itself. Updating WordPress does not fix them — the server’s PHP version has to be upgraded.

If PHP answers requests from the open internet, your security depends on how fast your host patches the runtime.

Sound familiar?

  • Unknown admin users or plugins appearing
  • PHP files hiding in wp-content/uploads
  • Spam pages or redirects in search results
  • Host suspensions or blacklist warnings

02 The solution

Split the house in two.

TodayFully exposed

Visitors and attackers

Anyone on the internet, bots included.

Public WordPress server

PHP runtime, theme, every plugin, wp-admin, xmlrpc.php and the REST API — all reachable.

Database

One compromised plugin away from your content and users.

With LunarCMS isolated

Visitors

Everyone still gets your full website.

Nuxt frontend on Cloudflare

Pre-rendered and edge-cached pages behind Cloudflare’s WAF and DDoS protection. No PHP, no database.

Private zone — no public address

Headless WordPress CMS

Reachable only through Cloudflare Tunnel and Access. Editors sign in with SSO, everyone else gets nothing.

Database

Never exposed, never queried by the public site.

WordPress still needs patching — but a vulnerability in a CMS nobody can reach is a maintenance task, not an emergency.

  • 0public PHP endpoints
  • 100%of your content kept
  • Edgedelivery from 300+ cities
  • SSOfor every editor login

03 How we do it

From breach to bulletproof.

  1. 01

    Triage & clean-up

    If you’ve been hit, we contain it first: hunt webshells and rogue accounts, rotate credentials and recover a clean content snapshot.

  2. 02

    Content & plugin audit

    We map every post type, custom field, form and plugin, and decide what moves to the frontend, what stays in the CMS and what goes.

  3. 03

    Nuxt rebuild

    Your site is rebuilt in Nuxt, pixel-faithful or redesigned, pulling content from the WordPress API — faster than it’s ever been.

  4. 04

    Lock down the CMS

    WordPress moves to a private host behind Cloudflare Tunnel and Access. wp-admin, xmlrpc and the API disappear from the public internet.

  5. 05

    Cut-over & watch

    We deploy the frontend to Cloudflare, switch DNS with zero downtime, wire publish-to-rebuild hooks and keep monitoring both sides.

04 Questions

Straight answers.

Will our editors have to learn anything new?
No. They keep using the WordPress dashboard they already know. The only change is that they sign in through a secure login page first, and hitting publish updates the live site automatically.
Does headless mean we never need to update WordPress again?
You still keep WordPress and PHP patched — we can manage that for you. The difference is urgency: a vulnerability in a CMS that has no public address can’t be exploited by drive-by bots.
What about forms, search and e-commerce?
Forms and search are rebuilt as secure serverless endpoints on Cloudflare. WooCommerce and membership sites are assessed case by case during the audit, and we’ll be upfront about what moves and what doesn’t.
Our site is already compromised. Can you still help?
Yes — that’s where most of these projects start. We contain the incident, recover clean content and then rebuild on the isolated architecture so the same door can’t be reopened.
Will we lose SEO rankings?
We preserve your URLs, metadata, sitemaps and redirects. Most clients see better Core Web Vitals after the move, which helps rankings rather than hurting them.

05 Contact us

Got an idea? Let’s launch it.

Research, prototype, launch. Tell us where you want to go and we’ll plot the route.

Studio

77 Lower Camden StreetSt Kevin’sDublin 2IrelandD02 XE80

0 / 5000