Is Page Builder Sandwich still maintained?
No. The WordPress.org directory closed Page Builder Sandwich on 1 March 2024, 2 years and 7 months ago, and gives the reason as "Security Issue". It does not publish what the issue is, and nothing here is our own assessment of the code. What is certain is that the listing is closed and no update can reach a site through WordPress while it stays that way.
The evidence
Every figure below is read from the WordPress.org plugin directory. Nothing here is our assessment of the code.
| Directory status | Closed by the plugin team, not available to install or update |
|---|---|
| Closed on | 1 March 2024 (2 years and 7 months ago) |
| Reason given | “Security Issue” |
| Closure | Not stated as permanent in the directory's notice |
| Read from the directory | 12 October 2026 |
Once a listing is closed the directory stops publishing its release date, tested-up-to version, install count and support figures, so the release details below come from the plugin's code archive instead.
What its code archive shows
| Last release | Version 6.34.13 (tagged 6 October 2026) |
|---|---|
| Tested up to | WordPress 7.1 |
| Requires | WordPress 6.8, PHP 8.2 |
| Releases in the archive | 84 |
| Read from | plugins.svn.wordpress.org/page-builder-sandwich, 12 October 2026 |
The directory keeps a closed plugin's code readable, and the last release tagged in Page Builder Sandwich's archive is version 6.34.13, tagged on 6 October 2026.
That release declared itself tested up to WordPress 7.1, which is still the current line. It asked for WordPress 6.8 and PHP 8.2 or later. So it was tested against current WordPress when it last shipped, but nothing further can follow it from the directory.
The archive holds 84 tagged releases, the oldest still there tagged on 15 February 2015. Its last release described the plugin in one line as: “Build pages from 48 blocks, section by section, in the block editor or Sandwich Studio, with clean front-end HTML and no builder wrappers.” That is the job something else has to take over on any site still running it.
Tag dates, almost always the day a release shipped. The count is the tags left, not every release ever made.
What these signals mean
A closed plugin is not a quiet one. A quiet plugin is still listed, and its author could ship a fix tomorrow. A closed one gets no update however long you wait, and the dashboard shows no sign of that: a plugin with no update available looks exactly like one that is up to date.
A security closure is the plugin team withdrawing a listing over a reported concern. The directory keeps the details to itself, and we have not examined the code, so this page does not say what the concern is or whether it affects your site. What the closure does establish is simple: while the listing stays closed, no fix can be delivered through WordPress.
The directory's closure notice does not say the closure is permanent. Listings closed for review can be reopened once the plugin team is satisfied, so the listing is worth checking again before you commit to a replacement. It has been closed for 2 years and 7 months, so a copy still installed has gone at least that long without an update through WordPress.
What to do about it
Put this one first. Check whether it is active on the site, and whether its author offers a fixed version through their own site; if neither answer is clear, plan the replacement now rather than waiting for the next upgrade. The directory withdrew it over a security concern, and there is no update route through WordPress to wait for.
Do not start by deleting it. Find out what depends on it, back up the database as well as the files, and test the replacement on a staging copy first, because deleting a plugin can run an uninstall routine that drops its tables.
The directory stops publishing a closed plugin's category, so this page does not suggest alternatives. Any replacement has to do the job that Page Builder Sandwich's last release, version 6.34.13, describes above. That release was tested against WordPress 7.1; one worth moving to is tested against 7.1.3 and still listed in the directory.
Is a site you look after running Page Builder Sandwich?
Our free WordPress plugin checker reads any public site and lists the plugins it loads, with the same maintenance signals as the table above for each one. No login and no signup, so it works on a client’s site before you have access to it.
Related plugin checks
- Is Elementor Website Builder still maintained? Updated 5 October 2026, current against recent WordPress. Nothing of concern.
- Is Spectra Legacy still maintained? Updated 9 October 2026, current against recent WordPress. Nothing of concern.
- Is Stackable still maintained? Updated 9 September 2026, current against recent WordPress. Nothing of concern.
Questions
Why was Page Builder Sandwich removed from the WordPress plugin directory?
The directory gives the reason as "Security Issue", quoted as it appears. It does not publish what the issue is. We have not assessed the code, so we cannot tell you what the concern was or whether it applies to the version on your site.
Will Page Builder Sandwich keep working if it is already installed?
Usually, for a while. Closing a listing removes the plugin from the directory; it does not reach into sites and switch anything off. What stops is updates, and they stopped on 1 March 2024: WordPress cannot offer an update for a plugin that is not listed, so the installed copy is frozen at whatever version it reached, which can be no later than 6.34.13, the last release in its archive. The dashboard gives no sign of that, because a plugin with no available update looks exactly like one that is up to date.
Could Page Builder Sandwich come back to the directory?
Possibly. The directory's closure notice does not say the closure is permanent, and the plugin team can reopen a listing once the reason for closing it has been dealt with. It had not been reopened when we read the directory on 12 October 2026.
Is Page Builder Sandwich a security risk?
The directory closed it and gives the reason as "Security Issue". That is the directory's statement, and it is the only one on this page: we do not know what the issue is, we have not tested the plugin, and nothing here is a security finding of ours. What it does justify is dealing with this plugin first on any site that runs it, because no fix can reach that site through WordPress while the listing is closed.
Read from the WordPress.org plugin directory on 12 October 2026. We report maintenance signals only, and never claim a plugin is insecure. All plugins we cover.