Sigma · CVE exploitation
PHP2Shell (CVE-2026-109618 / CVE-2026-109619): web request reads a PHP session file
- severity
- high
- confidence
- 75/100
- generated
- 14 Nov 2026
- Linked CVE
- CVE-2026-109618 · CVE-2026-109619
A request URI that names a PHP session file (sess_...) together with a path traversal, an absolute session directory or a php:// wrapper. The leaked PHP2Shell chain writes attacker data into the session file through upload progress and then includes that file; this is the include step as it shows up in a URL.
False-positive notes
Needs "sess_" AND one of ../ (plain or URL-encoded), /tmp/, /var/lib/php, a Windows temp path or php:// in the same URI. A session id in a cookie or a normal ?PHPSESSID= parameter does not contain sess_ and does not match. Only covers the include when the file name travels in the URL; a POST body include needs WAF payload logging. Needs raw request-URI logging (some servers normalise ../ away). Correlate with the HTTP status before calling it a compromise.
References
- skopnix.com/cve/CVE-2026-109618 ↗
- skopnix.com/cve/CVE-2026-109619 ↗
- www.php.net/archive/2026.php#2026-10-20-1 ↗
- cert.europa.eu/publications/security-advisories/2026-018/ ↗
- watchtowr.com/intelligence/php-cve-2026-109618-faq/ ↗
- nvd.nist.gov/vuln/detail/CVE-2026-109618 ↗
- nvd.nist.gov/vuln/detail/CVE-2026-109619 ↗
title: 'Skopnix - PHP2Shell (CVE-2026-109618 / CVE-2026-109619): web request reads a PHP session file'id: eb8e0562-840a-58a2-813f-2b9cd8e98b6dstatus: experimentaldescription: A request URI that names a PHP session file (sess_...) together with a path traversal, an absolute session directory or a php:// wrapper. The leaked PHP2Shell chain writes attacker data into the session file through upload progress and then includes that file; this is the include step as it shows up in a URL.references: - https://skopnix.com/cve/CVE-2026-109618 - https://skopnix.com/cve/CVE-2026-109619 - https://www.php.net/archive/2026.php#2026-10-20-1 - https://cert.europa.eu/publications/security-advisories/2026-018/ - https://watchtowr.com/intelligence/php-cve-2026-109618-faq/ - https://nvd.nist.gov/vuln/detail/CVE-2026-109618 - https://nvd.nist.gov/vuln/detail/CVE-2026-109619author: skopnixdate: '2026-11-14'tags: - attack.initial-access - attack.t1190 - cve.2026-109618 - cve.2026-109619logsource: category: webserverdetection: selection_sess: cs-uri-query|contains: sess_ selection_path: cs-uri-query|contains: - ../ - ..%2f - '%2e%2e' - /tmp/ - '%2ftmp%2f' - /var/lib/php - '%2fvar%2flib%2fphp' - php:// - php%3a%2f%2f - windows\temp - windows%5ctemp condition: selection_sess and selection_pathfalsepositives: - Vulnerability scanners and authorised penetration tests (attempts, not compromise)level: highskopnix-sigma-cve-cve-2026-109618-session-file-read-7bb658c7.yml
How to deploy on Sigma
- Step 1
- Convert for your SIEM with sigma-cli / pySigma, e.g. sigma convert -t splunk -p sysmon rule.yml.
- Step 2
- Run it as a hunt first: every rule ships as status experimental.
- Step 3
- Promote to an alert once a week of results is clean on your data.
- Check
- The processing pipeline must map the logsource (firewall, dns, proxy, webserver, process_creation) to your field names.