Responding to emerging PHP vulnerabilities: The value of a joined-up approach
3 min
When two critical PHP vulnerabilities emerged in October 2026, a coordinated response from Acquia and DCX helped protect client websites, resolve application-level risks and provide assurance that digital environments were being actively managed.
Website security isn't simply about keeping software up to date. It's about knowing how to respond when vulnerabilities emerge, taking responsibility for the necessary action and making sure potential risks are properly addressed.
On 21st October 2026, two critical vulnerabilities in PHP emerged ahead of their planned disclosure, prompting the release of emergency security patches. As the vulnerabilities affected PHP itself, rather than individual applications or websites, any site running an affected version was potentially exposed.
For organisations relying on their websites as important business and customer communication channels, this created an immediate need for action - and put their website support arrangements to the test.
Coordinated response, from platform to application
Acquia, the hosting platform underpinning the affected websites, responded by releasing emergency security patches to address the vulnerabilities, covering the affected PHP versions and ensuring the underlying hosting environment was updated.
However, platform-level patching was only part of the response. DCX recognised that it was important to establish whether every individual client website was protected, rather than simply assuming a patch being available meant the issue was resolved.
Our developers proactively reviewed affected client environments, checked the relevant patches had been applied successfully and validated that sites continued to function as expected.
Working through our established Incident Management process, technical teams assessed risks, coordinated checks and escalated any issues requiring further action.
At the same time, DCX account managers coordinated client communications, providing timely updates, answering questions and helping clients brief their own internal risk and leadership teams.
The priority was not just to address the technical issue, but to reassure clients that their websites were being actively monitored and that someone was taking ownership.
John Money, Director of Product Marketing at Acquia, commented:
"When a critical vulnerability is disclosed, customers should not have to choose between speed and certainty. Our role is to secure the platform. Paragon's role is to make sure every client knows exactly where they stand. That combination is what partnership should look like."
This distinction between platform responsibility and application-level ownership is a key part of an effective security response.
When a platform patch isn't enough
The incident also demonstrated why website security cannot always be resolved at hosting or platform level.
For one client, whose website was built using the Laravel framework and hosted outside Acquia, DCX needed to undertake the patching directly.
As a precaution, the website was taken offline while our developers applied the necessary updates, checked the application and validated the changes before restoring the service.
This is an important distinction. While a platform provider can address vulnerabilities within its infrastructure, it doesn’t necessarily resolve every issue within an individual website's framework, application or underlying code.
Having a digital partner who understands both sides of this relationship means potential problems can be identified, escalated and resolved without responsibility falling between different providers.
The value of a fast, joined-up response
For clients, the experience reinforced the importance of a website operating model that brings together platform expertise, hands-on technical delivery, incident management and proactive communication.
Client feedback highlighted the benefits of this coordinated operating model.
Rachael Ford, Head of Digital at Rathbones, said:
"Brilliant job team – it was fantastic to see that the team could answer all internal queries on this so fast. Appreciate the combined efforts."
Daniel Bell, Head of Design at Close Brothers, added:
"Thank you for the team's efforts today. I've highlighted the rapid response Acquia and yourselves took to stakeholders, showing the effectiveness of the website operating model."
Both comments underline an important point: clients don’t need to navigate technical vulnerabilities alone. They need a partner who can investigate, act, coordinate the right people and keep them informed.
More than an emergency response
Our responsiveness doesn’t begin when a critical vulnerability is announced. For many DCX clients, vulnerability monitoring, routine patching and technical maintenance are already managed through monthly BAU sprints.
Our Incident Management service provides a defined process for assessing severity, coordinating remediation and communicating progress. When urgent issues arise, developers and account managers work together to deliver a rapid, coordinated response.
The October incident showed the value of having these arrangements in place before they’re needed.
Three questions to ask your website partner
Security incidents like this are a useful reminder to look beyond the technology itself and consider how effectively your website support arrangements work. There are three important questions worth asking:
1. Who checks that a platform patch has actually been applied to your website?
A patch being released doesn't mean every website is protected automatically. Someone needs to validate that the update has been applied and the site is operating as expected.
2. Who owns the fix when a platform patch isn't enough?
Some issues require intervention beyond the hosting environment, including changes to the website framework, application or underlying code. There should be clear ownership when that happens.
3. How quickly will you hear from them?
During a security incident, a lack of communication creates uncertainty. You should know who is responsible for keeping you informed, what action is being taken and when you can expect the next update.
Security doesn't just mean applying patches
No website environment is entirely immune to emerging vulnerabilities. What matters is how quickly potential risks are identified, how effectively the right teams work together and whether issues are followed through to resolution.
The October PHP incident showed the value of a joined-up approach: Acquia’s platform-level patching, DCX developers’ hands-on validation and remediation, and account managers’ clear, timely communication – all supported by an established Incident Management process.
Because effective website management isn't just about keeping technology running. You need the right people, processes and expertise in place to respond when things go wrong and resolve issues with confidence.