<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: MyAppScan</title>
    <description>The latest articles on DEV Community by MyAppScan (@myappscan).</description>
    <link>https://dev.to/myappscan</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4259051%2Fd420b10d-aa8f-49f2-a7f2-a462e28ed904.png</url>
      <title>DEV Community: MyAppScan</title>
      <link>https://dev.to/myappscan</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/myappscan"/>
    <language>en</language>
    <item>
      <title>PHP2Shell: How to Identify Vulnerable PHP Backends Through Mobile App Security Testing</title>
      <dc:creator>MyAppScan</dc:creator>
      <pubDate>Sun, 22 Nov 2026 16:56:11 +0000</pubDate>
      <link>https://dev.to/myappscan/php2shell-how-to-identify-vulnerable-php-backends-through-mobile-app-security-testing-4be1</link>
      <guid>https://dev.to/myappscan/php2shell-how-to-identify-vulnerable-php-backends-through-mobile-app-security-testing-4be1</guid>
      <description>&lt;p&gt;PHP2Shell: How to Identify Vulnerable PHP Backends Through Mobile App Security Testing&lt;/p&gt;

&lt;p&gt;Mobile applications are often treated as standalone products, but most modern applications depend heavily on backend APIs.&lt;/p&gt;

&lt;p&gt;You can have a securely implemented Android or iOS application and still expose your users to serious security risks through vulnerable backend infrastructure.&lt;/p&gt;

&lt;p&gt;PHP2Shell is a good example of why mobile application security testing should go beyond the APK or IPA.&lt;/p&gt;

&lt;p&gt;In this article, we'll explore what PHP2Shell means for mobile applications, how to identify potentially affected PHP backends, and what penetration testers should investigate.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;What Is PHP2Shell?&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;PHP2Shell refers to two PHP runtime vulnerabilities:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;CVE-2026-109618&lt;/li&gt;
&lt;li&gt;CVE-2026-109619&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;These vulnerabilities can potentially lead to remote code execution (RCE) on affected PHP servers.&lt;/p&gt;

&lt;p&gt;The vulnerabilities target PHP runtime internals rather than a particular PHP framework or CMS.&lt;/p&gt;

&lt;p&gt;This means that applications using Laravel, Symfony, custom PHP APIs, or other PHP-based solutions may require investigation.&lt;/p&gt;

&lt;p&gt;The important distinction: PHP2Shell is a server-side vulnerability, not an Android or iOS vulnerability.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Can a Mobile Application Be Affected?&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Yes, indirectly.&lt;/p&gt;

&lt;p&gt;Consider a typical mobile application architecture:&lt;/p&gt;

&lt;p&gt;Android / iOS Application&lt;br&gt;
          |&lt;br&gt;
          | HTTPS&lt;br&gt;
          v&lt;br&gt;
       API Gateway&lt;br&gt;
          |&lt;br&gt;
          v&lt;br&gt;
       PHP Backend&lt;br&gt;
          |&lt;br&gt;
          v&lt;br&gt;
        Database&lt;/p&gt;

&lt;p&gt;The mobile application communicates with backend APIs over HTTPS.&lt;/p&gt;

&lt;p&gt;If those APIs are powered by a vulnerable PHP runtime, the backend infrastructure may be exposed.&lt;/p&gt;

&lt;p&gt;Potential consequences include:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Remote code execution on the server.&lt;/li&gt;
&lt;li&gt;Exposure of sensitive application data.&lt;/li&gt;
&lt;li&gt;Compromise of API credentials.&lt;/li&gt;
&lt;li&gt;Unauthorized access to backend resources.&lt;/li&gt;
&lt;li&gt;Service disruption.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This does not mean that an attacker can automatically execute code on the mobile device itself.&lt;/p&gt;

&lt;p&gt;The vulnerable component is the backend PHP runtime.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Step One: Identify Backend API Endpoints&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Start by identifying the endpoints used by the mobile application.&lt;/p&gt;

&lt;p&gt;Static Analysis&lt;/p&gt;

&lt;p&gt;For Android applications, useful tools include:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;JADX&lt;/li&gt;
&lt;li&gt;APKTool&lt;/li&gt;
&lt;li&gt;MobSF&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Search the decompiled application for:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://api.example.com" rel="noopener noreferrer"&gt;https://api.example.com&lt;/a&gt;&lt;br&gt;
&lt;a href="https://backend.example.com" rel="noopener noreferrer"&gt;https://backend.example.com&lt;/a&gt;&lt;br&gt;
/api/v1/&lt;br&gt;
/auth/login&lt;/p&gt;

&lt;p&gt;Look for:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;API base URLs.&lt;/li&gt;
&lt;li&gt;Authentication endpoints.&lt;/li&gt;
&lt;li&gt;File upload endpoints.&lt;/li&gt;
&lt;li&gt;WebView destinations.&lt;/li&gt;
&lt;li&gt;Third-party integrations.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;For iOS, inspect the application binary and associated configuration files using appropriate iOS static analysis tools.&lt;/p&gt;

&lt;p&gt;Remember that identifying an API hostname does not tell you which backend technology it uses.&lt;/p&gt;

&lt;p&gt;Dynamic Analysis&lt;/p&gt;

&lt;p&gt;Use Burp Suite or mitmproxy to intercept application traffic.&lt;/p&gt;

&lt;p&gt;Perform normal application operations:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Login and registration.&lt;/li&gt;
&lt;li&gt;Profile updates.&lt;/li&gt;
&lt;li&gt;File uploads.&lt;/li&gt;
&lt;li&gt;Image uploads.&lt;/li&gt;
&lt;li&gt;Password recovery.&lt;/li&gt;
&lt;li&gt;Data retrieval.&lt;/li&gt;
&lt;li&gt;Other authenticated operations.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Build an inventory of backend hosts and endpoints.&lt;/p&gt;

&lt;p&gt;This inventory becomes the foundation of the backend security assessment.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Step Two: Identify PHP Indicators&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Once you have identified the API endpoints, inspect their HTTP responses.&lt;/p&gt;

&lt;p&gt;For example:&lt;/p&gt;

&lt;p&gt;HTTP/2 200 OK&lt;br&gt;
Content-Type: application/json&lt;br&gt;
X-Powered-By: PHP/8.4.26&lt;/p&gt;

&lt;p&gt;Other possible indicators include:&lt;/p&gt;

&lt;p&gt;Set-Cookie: PHPSESSID=xxxxxxxx&lt;/p&gt;

&lt;p&gt;You may also encounter PHP-related error messages or PHP-specific endpoint paths.&lt;/p&gt;

&lt;p&gt;You can inspect response headers using:&lt;/p&gt;

&lt;p&gt;curl -I &lt;a href="https://api.example.com" rel="noopener noreferrer"&gt;https://api.example.com&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;However, these indicators are not conclusive.&lt;/p&gt;

&lt;p&gt;An application can remove its PHP headers, customize its session cookies, or expose extensionless API routes.&lt;/p&gt;

&lt;p&gt;No PHP header does not mean no PHP backend.&lt;/p&gt;

&lt;p&gt;Likewise, identifying PHP does not confirm PHP2Shell.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Step Three: Investigate Multipart Upload Endpoints&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;One particularly interesting area during PHP backend assessments is multipart request handling.&lt;/p&gt;

&lt;p&gt;PHP2Shell research describes attack paths involving PHP multipart request processing and session upload progress functionality.&lt;/p&gt;

&lt;p&gt;Mobile applications commonly use multipart requests for:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Profile pictures.&lt;/li&gt;
&lt;li&gt;Document uploads.&lt;/li&gt;
&lt;li&gt;Chat attachments.&lt;/li&gt;
&lt;li&gt;Image uploads.&lt;/li&gt;
&lt;li&gt;Import functionality.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;For example:&lt;/p&gt;

&lt;p&gt;POST /api/upload HTTP/1.1&lt;br&gt;
Host: api.example.com&lt;br&gt;
Content-Type: multipart/form-data; boundary=----Boundary&lt;/p&gt;

&lt;p&gt;------Boundary&lt;br&gt;
Content-Disposition: form-data; name="file"; filename="image.jpg"&lt;br&gt;
Content-Type: image/jpeg&lt;/p&gt;

&lt;p&gt;[FILE CONTENT]&lt;br&gt;
------Boundary--&lt;/p&gt;

&lt;p&gt;During testing, identify all endpoints accepting multipart/form-data.&lt;/p&gt;

&lt;p&gt;Investigate the backend's PHP configuration, especially:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;PHP session upload progress settings.&lt;/li&gt;
&lt;li&gt;PHP runtime version.&lt;/li&gt;
&lt;li&gt;PHP-FPM configuration.&lt;/li&gt;
&lt;li&gt;Request processing configuration.&lt;/li&gt;
&lt;li&gt;Memory limits.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Do not assume that every multipart endpoint is vulnerable. The actual exposure depends on the affected runtime and applicable conditions.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Step Four: Verify the PHP Runtime Version&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The next step is determining whether the backend uses an affected PHP release.&lt;/p&gt;

&lt;p&gt;The initial fixed releases for the affected branches were:&lt;/p&gt;

&lt;p&gt;PHP Branch| Initial fixed release&lt;br&gt;
PHP 8.5| 8.5.12&lt;br&gt;
PHP 8.4| 8.4.27&lt;br&gt;
PHP 8.3| 8.3.36&lt;br&gt;
PHP 8.2| 8.2.35&lt;/p&gt;

&lt;p&gt;For example, if an API response exposes:&lt;/p&gt;

&lt;p&gt;X-Powered-By: PHP/8.4.26&lt;/p&gt;

&lt;p&gt;This is a reason to investigate further.&lt;/p&gt;

&lt;p&gt;It is not sufficient evidence to report confirmed PHP2Shell exploitation.&lt;/p&gt;

&lt;p&gt;Ask the backend or infrastructure team to verify:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;The actual PHP runtime version.&lt;/li&gt;
&lt;li&gt;Whether the relevant security patches are installed.&lt;/li&gt;
&lt;li&gt;Whether all PHP workers are running the patched version.&lt;/li&gt;
&lt;li&gt;Whether the affected configuration and execution paths are present.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Always consult the official PHP security advisory for the latest releases and branch-specific guidance.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Can You Test PHP2Shell Through Burp Suite?&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Burp Suite is useful for identifying backend endpoints, examining HTTP requests, and understanding how the mobile application communicates with its server.&lt;/p&gt;

&lt;p&gt;However, Burp Suite alone cannot confirm whether the PHP runtime is vulnerable.&lt;/p&gt;

&lt;p&gt;A practical assessment workflow looks like this:&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;    Mobile Application
            |
            v
      Burp Suite
            |
            v
    Identify API Hosts
            |
            v
   Identify PHP Indicators
            |
            v
  Identify Multipart Endpoints
            |
            v
  Request Runtime Verification
            |
            v
   Validate Patch Status
            |
            v
   Report Confirmed Exposure
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;p&gt;Avoid blindly sending public proof-of-concept payloads to production APIs.&lt;/p&gt;

&lt;p&gt;PHP2Shell testing may involve memory corruption and resource exhaustion. Testing should be performed in an authorized environment with appropriate safeguards.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;How Should You Report It?&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;If you identify a potentially affected backend during a mobile application penetration test, document it separately from client-side vulnerabilities.&lt;/p&gt;

&lt;p&gt;Suggested finding:&lt;/p&gt;

&lt;p&gt;Title: Potential PHP2Shell Exposure in Mobile Application Backend&lt;/p&gt;

&lt;p&gt;Affected Component: Backend API infrastructure.&lt;/p&gt;

&lt;p&gt;Description:&lt;/p&gt;

&lt;p&gt;During the mobile application security assessment, API endpoints were identified that appear to use PHP.&lt;/p&gt;

&lt;p&gt;The backend may be running a PHP runtime affected by CVE-2026-109618 and CVE-2026-109619.&lt;/p&gt;

&lt;p&gt;If the affected runtime and configuration conditions are present, successful exploitation could result in remote code execution on the backend server.&lt;/p&gt;

&lt;p&gt;Recommendation:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Upgrade affected PHP installations to fixed releases.&lt;/li&gt;
&lt;li&gt;Verify PHP-FPM and other PHP worker processes have restarted.&lt;/li&gt;
&lt;li&gt;Review PHP configuration and session upload progress settings.&lt;/li&gt;
&lt;li&gt;Review server logs for suspicious activity.&lt;/li&gt;
&lt;li&gt;Investigate possible compromise if the server was exposed while vulnerable.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Important: Do not classify the issue as confirmed PHP2Shell solely because an HTTP response reveals an affected PHP version.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Scan Your Mobile Applications with MyAppScan&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Identifying backend vulnerabilities is only one part of a comprehensive mobile application security assessment. The mobile application itself also needs to be assessed for security weaknesses.&lt;/p&gt;

&lt;p&gt;If you're a developer, penetration tester, or security researcher looking for a way to analyze mobile application security, check out "MyAppScan" (&lt;a href="https://myappscan.com" rel="noopener noreferrer"&gt;https://myappscan.com&lt;/a&gt;).&lt;/p&gt;

&lt;p&gt;"&lt;a href="https://myappscan.com" rel="noopener noreferrer"&gt;https://myappscan.com&lt;/a&gt;" (&lt;a href="https://myappscan.com" rel="noopener noreferrer"&gt;https://myappscan.com&lt;/a&gt;)&lt;/p&gt;

&lt;p&gt;MyAppScan is an online mobile application vulnerability scanner designed to help identify potential security weaknesses in mobile applications.&lt;/p&gt;

&lt;p&gt;It provides an additional layer of security testing to help developers and security professionals assess their mobile applications and identify issues that may require further investigation.&lt;/p&gt;

&lt;p&gt;Whether you're developing a new mobile application or conducting a security assessment, MyAppScan can be a useful addition to your mobile application security toolkit.&lt;/p&gt;

&lt;p&gt;Give it a try: &lt;a href="https://myappscan.com" rel="noopener noreferrer"&gt;https://myappscan.com&lt;/a&gt;&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Final Thoughts&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Mobile application security is not limited to reverse engineering APKs, analyzing IPA files, or identifying insecure local storage.&lt;/p&gt;

&lt;p&gt;Backend infrastructure is an equally important part of the attack surface.&lt;/p&gt;

&lt;p&gt;PHP2Shell demonstrates why penetration testers should investigate the technologies powering mobile application APIs.&lt;/p&gt;

&lt;p&gt;The next time you perform a mobile application assessment, don't stop after identifying insecure client-side functionality.&lt;/p&gt;

&lt;p&gt;Investigate the backend.&lt;/p&gt;

&lt;p&gt;Because sometimes, the biggest vulnerability in a mobile application isn't inside the application at all.&lt;/p&gt;




&lt;p&gt;References&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;"PHP Official Website" (&lt;a href="https://www.php.net/" rel="noopener noreferrer"&gt;https://www.php.net/&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;"Calif Research – PHP2Shell" (&lt;a href="https://calif.io/php2shell/" rel="noopener noreferrer"&gt;https://calif.io/php2shell/&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;"Akamai – Understanding PHP2Shell" (&lt;a href="https://www.akamai.com/blog/security-research/understanding-php2shell-everything-you-need-to-know" rel="noopener noreferrer"&gt;https://www.akamai.com/blog/security-research/understanding-php2shell-everything-you-need-to-know&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;"Tenable – PHP2Shell Exploitability Analysis" (&lt;a href="https://www.tenable.com/blog/php2shell-one-week-later-why-one-exploit-doesnt-work-everywhere" rel="noopener noreferrer"&gt;https://www.tenable.com/blog/php2shell-one-week-later-why-one-exploit-doesnt-work-everywhere&lt;/a&gt;)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Disclaimer: This article is intended for authorized security testing and educational purposes only.&lt;/p&gt;

</description>
      <category>security</category>
      <category>ai</category>
      <category>php</category>
      <category>vulnerabilities</category>
    </item>
  </channel>
</rss>
