
Meet the Authors
PHP2Shell flaws in the PHP runtime can reach SAP data through the custom applications that customers connect to SAP.
Finding exposed applications starts with an inventory of every PHP application that touches SAP, including non-production environments.
Layer Seven's Cybersecurity Extension for SAP flags vulnerable Cloud Foundry applications and alerts on suspected misuse while fixes are under way.
Two critical vulnerabilities in the PHP runtime, known as PHP2Shell, could expose SAP data and credentials through applications connected to SAP. The PHP project patched them on October 21, and they are tracked as CVE-2026-109618 and CVE-2026-109619.
Although the vulnerabilities do not directly affect SAP’s core systems, Layer Seven Security says the exposure sits in applications customers add and connect to SAP, such as custom applications on SAP Business Technology Platform (BTP).
Because that exposure sits outside SAP’s own systems, organizations need a way to find the affected applications and watch for misuse. Layer Seven’s Cybersecurity Extension for SAP is designed to do both across the SAP landscape.
Why Runtime Vulnerabilities Are Hard to Contain in SAP Environments
In its advisory, Layer Seven explains that the flaws sit in the PHP runtime, the layer that executes a web application’s code, and not in any one application. Teams therefore cannot tell whether a system is affected by looking at the application or the framework it uses, and in some setups the application’s own login does not reliably stop an attack.
The exposure sits in the applications customers add around SAP. Layer Seven’s assessment names custom applications on BTP’s Cloud Foundry runtime that use a community or custom PHP buildpack, the package that supplies the PHP runtime. It also names custom PHP runtimes on SAP HANA XS Advanced, customer container workloads in Kyma, and external or partner-managed portals that connect to SAP.
An attacker who exploits the flaws runs code with the application’s own permissions, so the damage depends on what the application can reach. Reachable resources include its database credentials, access tokens, and service secrets, and the OData, REST, SOAP, or RFC interfaces it uses to talk to SAP.
The business consequences range from exposed SAP data to unauthorized transactions and outages in portals and integrations. Even when SAP’s own systems are up to date, an application with privileged access to production SAP can be a significant risk, because the attacker inherits whatever access the application already has.
Where the Cybersecurity Extension for SAP Fits in Vulnerability Response
Containing PHP2Shell depends on finding the exposed applications, coordinating the teams that own them, and spotting misuse while fixes are under way.
The first step is knowing which applications run an affected PHP version. Layer Seven advises an inventory of every PHP application that touches SAP, including test, disaster-recovery, and stopped applications that could be restarted, with internet-facing applications that have privileged SAP access first.
SAP’s Application Vulnerability Report (AVR) offers a starting point by scanning custom applications deployed to supported Cloud Foundry landscapes each week, though vulnerabilities in SAP’s core systems, databases, and operating systems need other tools.
Layer Seven’s Cybersecurity Extension for SAP (CES) can identify Cloud Foundry applications running vulnerable PHP versions, so teams can see their exposure and decide what to fix first. It also brings AVR findings into the same view as weaknesses in application servers, databases, hosts, and integration components, so SAP administration, security, development, and infrastructure teams can coordinate fixes from one picture.
Fixing takes time, and some applications cannot be patched immediately. Until each fix lands, the question becomes whether anyone is using the exposure.
CES reads security events from SAP BTP’s audit log service and Cloud Foundry. It raises alerts on suspicious sign-in attempts, changes to privileged roles or trust settings, use of service credentials, and changes to deployments and buildpacks, activity that may indicate attempted or successful exploitation.
Alerts can feed security information and event management (SIEM) platforms, bringing SAP threats into the central incident process of security operations teams.
What This Means for SAPinsiders
Application credentials set the SAP exposure. A flaw in a runtime SAP does not ship can still reach SAP data through the credentials and interfaces a custom application holds. Customers that extend SAP on BTP take on vulnerability management for the code and runtimes they add.
Inventory becomes part of vulnerability management. Flaws that sit beneath the application cannot be spotted from the application itself, so knowing what runs and who owns it matters before a disclosure arrives. The inventory extends to the applications customers build and connect to SAP, including environments outside production.
BTP applications add another vulnerability layer. SAP’s Application Vulnerability Report covers deployed Cloud Foundry applications and leaves core systems and operating systems to other tools. Security teams that already track those layers now track one more, with development teams among its owners.




