🚨 Critical PHP vulnerabilities are making headlines 🚨. Why should CEOs, SGs and Heads of Comms care?

Because PHP powers WordPress, used by a huge share of association and corporate websites.

WordPress is a CMS. Its job is to run your Public Website.

The real risk starts when the same WordPress environment is also used to run your Extranet or store your CRM, member and stakeholder data through plugins.

Your digital architecture should clearly separate:

1. Public website → CMS / WordPress

2. Member Extranet → dedicated Member Platform

3. Member & stakeholder data → dedicated CRM

If 2 (Member Extranet) and 3 (Database/CRM) are still running on WordPress (1), move them out ASAP.

For years, we, at Symantra, have warned organisations about putting these critical functions in the same environment.

A hacked website is serious. It can usually be restored.

But imagine your members’ data, confidential Extranet documents and user accounts being exposed or stolen.

Your Extranet is down.

Members are calling.

Your Board wants answers.

That is a very different crisis...

Patching fixes today’s vulnerability.

But separating your website (1), Extranet (2) and CRM (3) reduces tomorrow’s risk.

If your WordPress website is attacked, separating these systems reduces the risk of exposing everything.

Still running your Member Extranet (2) or CRM database (3) on your WordPress?

The time to migrate is NOW.

👉 Contact Symantra to assess your current setup and securely migrate your Member Extranet and CRM data away from WordPress or other vulnerable CMS environments.

Symantra has extensive experience migrating membership organisations and corporates from legacy CMS based Extranets and plugin based databases to dedicated CRM and Member Platform environments.