Fewer strangers on the server
Replace Risky WordPress Plugins: Which to Keep, Which to Rewrite and What It Costs
Every plugin is a small contract with a stranger: you run their code on your server, and they promise to fix it when something goes wrong. Most keep the promise. The trouble is the ones who stopped answering, and the plugin you installed for one feature that ships forty others.
November 19, 2026 · 9 min read
- PassStore and payment gateway, released last monthkeep
- FailForm-to-email add-on, open advisory, no patchswitch off now
- FailSlider used on one page, no release in 3 yearsreplace
- WarnPopup tool loading scripts on every pagerewrite small
- WarnBackup plugin duplicating the host's backupsremove
- PassForms plugin staff edit weekly, maintainedkeep
The short answer
Replacing risky WordPress plugins means scoring each plugin on what it can reach, how it is maintained and how much of it you use, then rewriting the few small, high-risk jobs as lean custom code. Large, well-maintained plugins usually stay. Patchstack, a WordPress security seller, found 46 percent of 2025's newly found WordPress flaws had no patch when disclosed, which is why abandoned plugins go first.
On this page
- The security plugin installed to protect the other plugins
- The weeks when updating does nothing
- Scoring each plugin before anyone writes code
- Plugins worth keeping, even on a security page
- What a rewrite costs, and the bill it shrinks
- If malware is already on the site, clean before you rewrite
- When the plugin list says rebuild, not repair
The security plugin installed to protect the other plugins
Picture a bakery's website. A theme, a page builder, a store, two form plugins, a slider used on one page, a popup tool, a plugin that adds a map, and a security plugin installed after a scare, whose main job is to watch the other twenty. The security plugin is code from a stranger too. So is the plugin that hides the security plugin's nagging notices. Somewhere along the way the site stopped being a website and became a neighborhood association.
The numbers explain why that neighborhood needs watching. Patchstack, a company that sells WordPress security, reported in its State of WordPress Security in 2026 whitepaper, updated February 25, 2026, that it counted 11,334 new vulnerabilities in the WordPress ecosystem during 2025, a 42 percent jump over 2024. Plugins carried 91 percent of them and themes 9 percent; WordPress core accounted for just 6 reported flaws.
Read those figures for what they are: flaws discovered, not sites broken into. Our page on plugin security explains that distinction at length. The practical message is narrower and still blunt. WordPress itself is rarely the weak point. The add-ons are, and each one you remove is one less vendor whose bad week becomes yours. An abandoned plugin can also hold the whole site on old PHP, which is why we wrote about finding the plugin that blocks your PHP upgrade.
The weeks when updating does nothing
The standard advice is to keep everything updated, and it is good advice. It assumes an update exists. The same Patchstack report found that 46 percent of the 2025 vulnerabilities had no fix from the developer when they were made public. For those, the flaw is known to attackers and your update button has nothing to offer. Your choices shrink to three: switch the plugin off, block the attack in front of the site, or replace the plugin.
This is the same trust problem that hit much larger sites in November. Optimizely told BleepingComputer, in a statement reported November 16, 2026, that the flaw was in "the Experimentation account signup flow", and its customers' websites inherited the consequences without doing anything wrong. A plugin vendor sits in exactly that position on your server. Our write-up of the Optimizely hack shows how fast a trusted vendor can become the way in.
Scoring each plugin before anyone writes code
We do not replace plugins by count. A site with thirty well-kept plugins can be safer than one with eight neglected ones. Every plugin gets the same six questions, and the answers decide its fate. The goal is a short list of replacements that buy the most risk reduction per dollar.
| Question | Lower risk | Higher risk |
|---|---|---|
| What can it reach? | Display only: a gallery, a layout block | Payments, logins, customer records, file uploads or admin settings |
| Does it put scripts on public pages? | Nothing loads for visitors | Its own scripts on every page, including checkout |
| Is it maintained? | Regular releases and a way to report security bugs | No release in years, or a developer who has gone quiet |
| What is its advisory history? | Rare issues, fixed quickly | Repeated flaws, or one open now with no patch |
| How much of it do you use? | Most of its features | One feature out of dozens, the rest dead weight |
| How hard is the job to write? | A big product with years of edge cases | A small task a developer can write in a day or two |
The plugins that come out of this table worst are usually small: a form-to-email add-on, a popup tool, a snippet inserter, a shortcode pack, a map embed. They reach something sensitive, carry far more code than the job needs and could be written for your site in a fraction of the size. Those are the rewrites that pay.

Plugins worth keeping, even on a security page
A security page that tells you to rip out every plugin is selling something, and it is usually a rebuild. Some plugins are among the cheapest, best-tested parts of the site. Replacing them with custom code would trade a product many developers test for one only your developer reads.
The store and its payment gateways
Large, actively developed and widely used. Keep them current and keep card entry in the payment company's hosted fields.
Forms your team builds every week
If staff create and edit forms themselves, a maintained forms plugin is worth its keep. Replace only the small add-ons bolted onto it.
Anything your host already runs
Backups, firewalls and caching handled at the host level do not need a second plugin doing the same job inside WordPress.
Anything on a site you are leaving
If a move off WordPress is on the calendar, spend on the move, not on rewriting plugins the new site will not need.
Telling one big plugin from twenty small ones is half the value of a review. For the speed side of the same question, our guide to replacing plugin bloat sorts plugins by overlap and performance; this page sorts them by what they can reach.
What a rewrite costs, and the bill it shrinks
A replacement starts from $575, depending on complexity, with a written estimate before work starts. One small job, such as a form that emails the office and saves a copy, sits at the low end. Several jobs rolled into one custom plugin, or anything that touches orders or member accounts, costs more, and the estimate says how much and why. The custom plugin development page explains how we build.
- 1
Write it on a staging copy
The replacement is built to WordPress.org's security handbook, doing only the job you need, beside the old plugin.
- 2
Move the data across
Saved entries, settings and anything the old plugin stored are migrated, and checked against the original.
- 3
Remove the old plugin cleanly
Deactivated, deleted, and its leftover settings and database tables removed, so nothing stays behind for an attacker to find.
- 4
Test the paths that make money
Forms, checkout, bookings and logins, on desktop and iPhone, before the change reaches the live site.
- 5
Hand over the code
You own it. It is documented so any competent developer can maintain it, not only us.
What it saves is real but should not be oversold. You stop renewing a license for a plugin you used one feature of. You drop a vendor whose advisories you had to track. Visitors download less code if the old plugin loaded scripts on every page. What it does not do is make the site unhackable. Custom code has fewer eyes on it than a popular plugin, which is why we write it to a checklist and why it still needs updates when WordPress changes. Our hosting and maintenance plans, from $55 a month, cover the routine as that page describes.
If malware is already on the site, clean before you rewrite
Rewriting a plugin on an infected site is redecorating a house with the burglar still upstairs. Cleanup comes first. For WordPress, our fixed-price Fix it now malware cleanup is $349, paid online, starting within one business day of payment, with a full refund if we cannot fix it. Fix it now explains the terms, and our WordPress malware removal page covers what the cleanup includes.
If the infection reached the scripts on your pages, especially a checkout, read our script compromise response page, and talk to your attorney, insurer and payment processor before telling customers anything; this is not legal advice. Larger cleanups fall under malware removal and website security. Once the site is clean, the plugin review helps show which door the intruder likely used and whether to replace it.
When the plugin list says rebuild, not repair
Sometimes the scoring table comes back with half the plugins marked high risk and the page builder holding everything together. Replacing plugins one at a time on that site is mopping during a leak. The honest recommendation is a site that does not need them, and we will say so in the estimate rather than sell you six rewrites first.
- More than a handful of plugins score high risk and they do jobs the business cannot do without.
- The page builder is the site, so every rewrite has to work around it.
- You need a strict browser policy, and the plugins keep adding scripts it has to make room for.
- Updates break something most months, even after cleanup.
If that list fits, compare WordPress to Next.js and Athena versus WordPress, our content system built into every custom site we make. A site built that way loads only the scripts chosen for it, which makes a strict Content Security Policy practical from launch. For everything a plugin review touches, from a third-party script audit to ongoing script monitoring, see our website security services and the WordPress plugins section.
DataCram is a web studio in San Antonio, Texas, building for the web since 1999, working with businesses across the US by phone, video and a shared project page. Call (210) 346-0848, or start with the free website health check.
Questions owners ask about website security
Look at what each plugin can reach, whether it has had a release recently, whether it has a public advisory open and how much of it you actually use. A plugin that handles payments, logins or uploads and has gone quiet is the first to review. Size alone does not decide it; neglect and reach do.
Not automatically. Custom code written to WordPress.org's security handbook does one job with far less code and no outside vendor, which lowers exposure. A popular plugin, though, gets read by many researchers, while your custom code has your developer. That is why we keep big, well-run plugins and rewrite small, risky ones.
Switch it off on a staging copy to see what breaks, then switch it off on the live site if you can live without it. If it runs something essential, block the attack in front of the site while a replacement is written. Patchstack found 46 percent of 2025's WordPress flaws had no patch when disclosed, so this happens often.
From $575, depending on complexity, with a written estimate before work starts. A single small job is at the low end; several jobs combined, or anything touching orders or accounts, costs more. A plugin conflict that only needs fixing, not replacing, is cheaper still.
It can, which is why we never remove a plugin on the live site first. Each removal is tested on a staging copy, with forms, checkout, bookings and logins checked on desktop and iPhone. The old plugin's data is moved before it goes, and its leftover settings are cleared afterward.
If a few small plugins carry most of the risk, replace those and stay. If many score high risk, the page builder holds the site together and updates break things monthly, a rebuild is usually the better money. We say which in the estimate, even when it means less work for us.
Keep reading
- Careful code, honest numbersWordPress Plugin Security: What the Handbook Requires, What the Vulnerability Numbers Actually MeasureWordPress plugin security explained from WordPress.org's handbook and Patchstack's 2025 data, read correctly, plus what we check in every plugin we write.
- Fewer moving partsToo Many WordPress Plugins? How to Replace Several Overlapping Ones With One That FitsToo many WordPress plugins slow sites and collide on updates. How to sort keep, merge and delete, what one plugin can replace, and when a rebuild wins.
- Start with the listThird-Party Script Audit: Every Script on Your Website, Who Owns It, and Whether It StaysWhat scripts are on your website? We load pages in real browsers, list every script with its owner and reach, and mark each one cut, keep or lock down.
- The browser's guest listContent Security Policy Setup: Listen First, Enforce Second, and Stop Trusting Whole VendorsCSP setup in order: report-only first, nonces over whole vendor domains, a hard look at 'unsafe-eval', and honest notes for WordPress and site builders.
- Card rules, in plain EnglishPCI DSS 6.4.3 and 11.6.1: Payment Page Script Records Your Processor Can Actually ReadWhat PCI DSS 6.4.3 and 11.6.1 ask of your payment page, how your checkout setup sets scope, and the records we build. We are not a QSA and do not certify.
- Tests that stay homeServer-Side A/B Testing: Run Experiments Without Handing a Vendor Every PageServer-side A/B testing picks the version before the page is sent, so no testing script runs in the browser. When to switch, when to keep your tool.
- Everything in Website SecuritySee the section
From the Insights desk
- The Optimizely Hack Was Not an Outage. It Was a Delivery.On November 16, a flaw in Optimizely's sign-up flow let an attacker slip card skimmers, wallet swappers and iPhone exploits into the testing scripts of 178 organizations, the BBC and Zoom among them. How it happened, what it did, and the fixes, in order.
- Why Your WordPress Form Gets Spammed — and the Fix That Doesn't Annoy Real CustomersForm spam isn't the problem — it's what the spam does: buried leads, a poisoned CRM, and an inbox you've learned to ignore. Why CAPTCHAs make it worse, and the silent fix that stops bots without costing you real customers.
Find the plugins worth replacing
Send us your plugin list or your site address. Someone at DataCram replies the same business day with what a plugin review covers and what an estimate would include.
Which of these sounds like you? (pick any)
Rather talk now? Call (210) 346-0848.