Revenue Growth Playbooks
Getting Paid for WordPress Security
Turn rising security costs into recurring revenue, higher retention and stronger customer relationships.
Security is no longer something hosting providers can leave entirely to their customers. When vulnerabilities hit PHP, WordPress or the underlying server, the host holds the patch and increasingly the responsibility. But security does not have to be a pure cost centre.
These three playbooks show how to monetise legacy PHP, package website protection and bring abandoned WordPress sites back into active maintenance. Each combines ShareShift's view of the European web with public market research and an illustrative business case.
Target
Hosting Product & Commercial Leaders
Focus
Security Monetisation
Author
Nadya Frost
The opportunity
Security is a business problem. It can also be a revenue opportunity.
2026 has made one thing clear: security is no longer optional infrastructure maintenance. Hosting operators are responsible for patching vulnerabilities, protecting shared environments and dealing with the consequences when customer websites are compromised.
The commercial opportunity is significant.
ShareShift's November 2026 scan found that approximately 40% of European websites disclosing their PHP version still run on outdated branches. That is a substantial installed base requiring host-level intervention, extended support or eventual modernisation.
Applying three complementary security plays on a host's installed base can generate over €250,000 per 10,000 eligible sites in year 1.
| Opportunity | Target | First-year revenue per 10k sites |
|---|---|---|
| 1. Monetize legacy sites | Old PHP installations | €146,500 |
| 2. Make security a value-add | Premium WP sites | €39,600 |
| 3. Bring abandoned sites back to life | Neglected WP installations | €72,000 |
| Total | €258,100 |
Playbook 1
Monetise the legacy with Extended PHP Support
Keeping websites running on old PHP safe is, increasingly, the hosting operator's responsibility. But it doesn't have to translate into a cost, too. Extended PHP support creates a bridge. Customers pay to keep their existing environment maintained while preparing for an upgrade. Current observed product prices range from €0.8 to €27 per month, depending on the market, PHP version and provider (see next section).
Market Insight
As of November 2026, 40.5% of sites with a visible PHP version are on 8.1 or lower. That customer base is "stuck" because forcing an upgrade risks breaking their websites. Doing nothing leaves the host carrying the security and compatibility risk.
Objective: Turn unsupported PHP versions into a paid support service and a pipeline for modernisation.
Segmentation: Identify customers running PHP branches that are no longer actively supported upstream. Cross-reference PHP branch with WordPress core version to identify three customer segments:
- Stuck: Old PHP, current or near-current WordPress. Likely constrained by plugins, themes or compatibility.
- Abandoned: Old PHP and old WordPress core. Likely needs a broader maintenance intervention to prevent full churn.
- Healthy: Current PHP. Better suited to the security bundle in Playbook 2, or to the managed hosting tier in Playbook 3.
Campaign: “Your website doesn't need to break to stay secure.”
Business case: applying assumptions from prior operational experience, c. 15% of customers can upgrade to hardened PHP, and 5% more can pay a one-off fee so the host helps them do it. In an illustrative case where the recurring product is priced at of € 4 / month, and the one-off service at €149, hardened PHP generates €146,500 per 10,000 eligible domains.
Product Packaging
Do not charge per security patch or force an immediate paid-product upgrade. Instead, introduce a three-step commercial offer that balances revenue generation, customer value and security risk mitigation:
- Free self-service upgrade tools, including staging and one-click rollback. Make extended support explicitly temporary. Publish the date of paid Hardened PHP support rollout per branch, to add urgency.
- One-off PHP and WordPress modernisation services for customers ready to move forward but needing assistance. This creates immediate revenue in-flow. In our example, even a 5% CVR brings in €74,500 immediate ROI per 10,000 old PHP sites.
- Paid Hardened PHP support, priced according to the age of the PHP branch. Billing is automated after a grace period allowing for free upgrades to occur. Even with a flat fee of €4/month, a 15% conversion rate on a 10,000 pool of eligible sites generates €72,000 Expansion ARR.
Research: The invisible patch
What are other hosts charging for PHP support?
Extended PHP support is already a monetised category, rather than a hypothetical product.
The customer does not see the work involved in keeping an old environment safe. This is the invisible patch. If a host is providing that value, it should be communicated and monetised.
| Provider | Published price | Coverage |
|---|---|---|
| easyname | €3.99/month | PHP 8.0 |
| easyname | €8.99/month | PHP 7.0 to 7.4 |
| easyname | €13.99/month | PHP 5.2 to 5.6 |
| Arsys | €7/month | PHP 8.1 |
| Arsys | €15/month | PHP 7.x and 8.0 |
| Arsys | €18/month | PHP 5.6 |
| one.com | €5.99/month | PHP 8.0-8.1 |
Prices often rise with the age of the PHP branch. This creates a natural incentive for customers to modernise rather than remain on legacy infras indefinitely.
For reference, Easyname prices start at €3,99 / month, Arsys ranges from €7 to €15 / month, while its sister brand IONOS goes as high as €27 / month for 4.x PHP. In CEE, Webglobe sets the floor with €0.79 - €2.49 / month, and the pan-regional one.com charges a flat fee of €5.99 / month for 8.0 - 8.1 support only.
The economics are particularly attractive for reseller hosting operators. Extended-support costs can be priced per server, while revenue is generated per customer. For example, InMotion resells TuxCare PHP Extended Lifecycle Support for $12 per server per month. At an illustrative 250 accounts per server, that is less than five cents per account monthly.
Next Step
Size your legacy PHP opportunity.
ShareShift can segment your detected PHP footprint and cross-reference it with WordPress versions, helping your team prioritise accounts for extended support and modernisation. Within this "stuck website" audience, we additionally prioritise commercial websites and higher-value customers based on our proprietary "digital footprint" methodology. Regardless of how modest is their hosting bill with you, we find customers who will care about the security and stability of their website.
Get in touch today, to find out how many sites are eligible for hardened PHP in your customer base.
Playbook 2
Make Advanced Security a Value-Add
Security sold solely as an optional add-on protects only the customers who buy it. But making protection available to every customer is not a pure cost increase, either. Less malware means lower support costs. As a reference, InMotion has reported a 40% reduction in security-related support cases after deploying malware protection on its shared hosting fleet.
If you're looking for ways to generate actual revenue from security protection, we recommend introducing a base level for the entire hosting portfolio first. You can then monetise advanced protection, vulnerability management and human-assisted recovery through premium offerings.
Vendor Insight
The market is already moving in this direction. In Monarx's review of 65 hosting providers, 37 included advanced protection in their plans, 31 sold a separate security product and 18 did both. Only 20 providers published prices, with entry-level add-ons ranging from $1.92 to $7.99 per site per month.
Objective: Fund universal protection through a tiered security offering that creates incremental recurring revenue.
Segmentation: Upsell customers with the strongest reasons to buy additional protection, such as:
- Sites running on premium infrastructure without same-tier security products
- WordPress sites with active commercial functionality and identifiable vulnerabilities (outdated plugins, older WP core, etc.).
Here, again, ShareShift's Commercial Tech Score and digital footprint signals can help identify customers with something valuable to protect, rather than selling security indiscriminately.
Campaign: “Your business is thriving online. Make sure it stays that way.”
Business case: Assuming an overall 5% attach rate of security products, and an 80/20 split between two product variants, extra ARR generated per 10,000 eligible sites is nearly €40,000 per year. Replace these with your own assumptions based on observed take rates and audience splits.
Product Packaging
Security needs to be sold and packaged not on features, based on value: reduced risk, peace of mind, clear responsibility in case of an emergency, etc. Consider creating a three-tier security proposition:
- Included: Baseline malware detection, automated file cleanup and security visibility for every hosting customer.
- Proactive Protection: Advanced malware detection, website protection and vulnerability monitoring.
- Managed Recovery: Everything in Proactive Protection, plus human-assisted cleanup, remediation and recovery.
Industry example: Consider Bluehost's hybrid strategy of bundling security features into hosting , plus carrying a standalone product for the highest level of protection.
Ready to find the opportunity in your own portfolio?
Prioritise accounts for advanced security protection based on what is actually running on their websites, not (only) what customers are paying you for.
Limitations
Protection is Not Patching
Patchstack's State of WordPress Security 2026 found that typical hosting defences blocked only 12% to 26% of known WordPress exploits in its test. Monarx also acknowledges that PHP2Shell vulnerabilities can trigger before its runtime protection intervenes.
A security bundle therefore addresses the layer above infrastructure patching: malware that gets through, vulnerable plugins, detection and recovery. The lesson is to sell a layered security proposition, not a promise that one product makes a website invulnerable.
Playbook 3
Bring abandoned sites back to life
Whether the owner lacks the skills, time or incentive to upgrade, an abandoned website is more than a steady-state account. It is a security liability on shared infrastructure. And a potential source of hosting revenue.
A managed maintenance subscription changes the relationship: instead of expecting customers to manage their own security, the host takes responsibility for keeping the site operational. Support costs go down, revenue and customer satisfaction increase.
Market Insight
ShareShift found that 22% of all European WordPress sites run a core more than one major release behind. That is 29% of the sites that show a version, or nearly 1 million sites. Nearly a quarter of active sites do not show their WP core version, so the total opportunity is even larger.
Objective: Convert neglected WordPress installations into maintained, paying subscriptions.
Segmentation: Identify WordPress websites running old WordPress core 4.x and 5.x and sites with outdated plugins or missing maintenance signals. Separate sites constrained by old PHP from those with current PHP but outdated WordPress core. The former should first receive the Hardened PHP offer in Playbook 1. The latter are the primary target for managed maintenance.
Within the resulting audience, you can further differentiate by willingness to pay:
- Abandoned inactive sites. Old WP core, old PHP, low plugin density, low content. These sites are unlikely to be revived, no matter the offer. Exclude.
- Steady-state old sites. Partially outdated, basic websites receiving routine content updates.
- Top-tier legacy sites. More advanced in their digital footprint, e.g. processing payments or a consent management tool. These are likely business customers stuck with a website they cannot maintain.
Campaign: “We'll make sure your website is properly looked after. We will update, test and roll back if something breaks.”
Business case: Assuming a € 3 / month gain in the hosting plan price, and a mix of opt-in and opt-out upgrades, a 10,000 WP audience can generate up to € 72,000 in extra ARR. Opt-outs are, as always, subject to contract terms and notice requirements. Feel free to enter your own pricing and take rate assumptions to generate a personalized business case.
Product Packaging
Offer an affordable Maintained WordPress subscription that includes automatic core and plugin updates, a staging environment and compatibility testing, backups and one-click rollback, vulnerability protection, and basic maintenance monitoring.
This plan should target abandoned and legacy sites directly, as an entry-level offering. Further upgrades may include a fuller Managed WordPress offering, which combines proactive security with performance boosts and multi-site management functions. Service-based companies can take it a step further and introduce a full-on human management service as the top tier for DIFM (do-it-for-me) customers. See next section for pricing benchmarks.
Research: Managed or Maintained?
What other hosts offer as WordPress Hosting?
We benchmarked the top 25 retail hosting brands servicing Europe. Security is only one of several dimensions for differentiation, though how comparable these offerings are sits outside the scope of this paper.
Security-led WordPress offerings split into three distinct packaging models: automated single-site containers, application-aware managed platforms, and multi-site agency setups. List prices range widely, gradually climbing as maintenance and governance move up the stack.
Tier 1: Automated Shared Hosting
What You Get: Pre-installed WordPress on isolated containers or shared servers with unattended core/plugin auto-updates, basic malware scanning, WAF/DDoS protection, and nightly backups; broken update layouts require manual recovery.
Examples: IONOS Hosting for WordPress, Strato Managed WordPress, Namecheap EasyWP.
Tier 2: Managed Application Hosting
What You Get: Application-aware maintenance with visual regression testing and rollback, operator-verified updates with 4-hour backups, staging environment, specialist support hours.
Examples: One.com Managed Hosting for WordPress, Aruba Managed WordPress Hosting, Register.it Managed Hosting for WordPress.
Tier 3: Multi-Site & Agency
Multi-site hosting (from 5 to unlimited sites) aimed at agencies and developers, shifting security above the single site layer through role-based access, isolated site/database boundaries, backup & snapshot control.
Examples: Hostinger Managed WordPress, Fasthosts Pro, OVHcloud Web Hosting for Agencies, Hostpoint Flex M.
Counter-perspective
Security Is Not Standardized Beneath the Label
Checklist badges like "auto-updates" and "malware protection" hide sharp differences in risk transfer. Entry plans often detect vulnerabilities or run blind updates that can break storefronts, while automated cleanup, visual rollback checks, and deep backup retention are gated behind higher tiers or add-ons; smaller hosts can win by selling verified safe updates and proactive remediation instead of passive alerts.
From insight to execution
Your security segments are already visible
ShareShift tracks the technical footprint of millions of European websites through weekly DNS, HTTP and TLS scans. For hosting operators, this means you can move beyond broad security campaigns and identify the specific accounts that need each service.
Playbook 1
Find the legacy
Segment WordPress accounts by detected PHP branch and core version.
Playbook 2
Find the growth
Identify businesses with meaningful commercial technology but no corresponding premium protection.
Playbook 3
Find the abandoned
Identify old WordPress installations that may need maintenance and managed recovery.
Instead of sending the same security offer to every customer, your commercial team can prioritise accounts based on what is actually running on their websites. Every segment becomes an actionable campaign audience. Get in touch today to size up each playbook within your customer base.
Appendix: BACKGROUND
What happened in 2026? The security incidents behind the opportunity
The commercial case is not hypothetical. Hosting operators have had to respond to a succession of critical vulnerabilities affecting shared infrastructure, control panels and WordPress installations.
| Date | Incident | What happened |
|---|---|---|
| 28 April | cPanel CVE-2026-41940 | Authentication bypass. Hosts reported exploitation attempts predating public disclosure and restricted access while patching. |
| Early July | Januscape and Bad Epoll | Critical Linux kernel vulnerabilities that could allow customer-to-customer or user-to-root escalation. Fixing them required kernel updates and reboots. |
| 17 July | WP2Shell | Unauthenticated code execution on a default WordPress installation. WordPress forced automatic updates. |
| 8 September | cPanel EmailTrack | An account with mail privileges could execute code as root. |
| 21 October | PHP2Shell | Two critical PHP vulnerabilities, CVSS 9.2. On shared hosting, customers depended on their host or PHP supplier for the fix. |
Appendix: Related Research