PHP2Shell: The Behind-the-Scenes Work of Protecting Digital Collections

PHP2Shell: The Behind-the-Scenes Work of Protecting Digital Collections

November 20, 2026

How Veridian responded to PHP2Shell and what goes on behind the scenes to keep digital collections secure and accessible.

Last month (October 2026) the discovery of critical security vulnerabilities known as PHP2Shell led organizations worldwide to review their systems, apply security updates, and, in some cases, temporarily restrict access to online services.

Although the core Veridian platform was not affected, our team's response provides an example of the ongoing cybersecurity work involved in protecting client collections and maintaining reliable access for researchers and the public.

What was PHP2Shell?

PHP2Shell refers to two critical vulnerabilities in PHP, a programming language widely used by websites and online applications, including content management systems such as WordPress, Drupal, and Joomla.

On October 21, 2026, the vulnerabilities were formally identified as CVE-2026-109618 and CVE-2026-109619, each receiving a critical severity rating of 9.2 out of 10.

The vulnerabilities involved weaknesses in how PHP manages computer memory. Under certain conditions, they could allow an attacker to execute unauthorized code on an affected server without needing a username or password. Successful exploitation could potentially expose sensitive information, compromise website functionality, or disrupt online services.

How were organizations affected?

Several organizations took precautionary measures that temporarily affected access to their online services.

  • At the University of Auckland, a notice on October 23 advised that access to some websites and services had been restricted as a precaution. Certain applications were temporarily available only on campus or through a VPN while its Digital Services team assessed the issue.

  • In the United States, Miami University in Ohio coordinated a response involving its IT teams, academic departments, and library personnel. Security patches were applied where possible, while some servers were temporarily shut down or removed from direct internet access.

  • Education technology provider Open LMS also temporarily took more than 2,000 hosted client sites offline while security updates were implemented. Its subsequent investigation found no evidence of suspicious activity across those sites.

These examples illustrate how addressing a security vulnerability can temporarily affect the availability of online services, even when there is no evidence that a system has been compromised.

For libraries and cultural heritage organizations, maintaining access is an important consideration. Their digital collections support research, education, and public engagement, often serving users across different locations and time zones.

How our team responded to PHP2Shell

We have established processes for regularly monitoring security advisories and newly identified software vulnerabilities, including those recorded through the Common Vulnerabilities and Exposures (CVE) system.

This monitoring helps our team identify potential security issues, assess their relevance to client environments, and determine what course of action is required. Through this process, our team became aware of PHP2Shell and began reviewing its potential impact on the systems we manage.

The core Veridian Software platform does not use PHP and was therefore not vulnerable to PHP2Shell.

However, some client collections incorporate customizations and third-party technologies, including WordPress-based components, that rely on PHP.

Our team reviewed these additional components to identify any potential exposure. Where vulnerable components were identified, the necessary security patches were quickly applied. Following that, the team reviewed system logs and our monitoring tools for any evidence of suspicious activity or attempted exploitation.

No security incidents were identified across our client environments.

Keeping ahead of emerging security threats

PHP2Shell is one example of the security vulnerabilities that software providers and organizations managing online services need to monitor. New vulnerabilities are regularly discovered in operating systems, web applications, and third-party technologies, with AI accelerating the pace at which vulnerabilities can be identified and exploited. Not every vulnerability presents the same level of risk, and not every system will be affected.

Effective vulnerability management involves understanding which technologies are in use, assessing the relevance and severity of newly identified issues, and determining the appropriate response. For our team, this work includes regularly reviewing security advisories, monitoring relevant CVEs, assessing potential exposure, and applying security updates where required.

These activities form part of the ongoing technical management and support of client collections. Much of this work takes place behind the scenes, alongside regular maintenance, infrastructure monitoring, and other measures that support the availability, security, and performance of digital collections.

Want to know more about how we protect client collections?

Related reading