Skip to content
skopnix
← Sigma detections

Sigma · CVE exploitation

PHP web stack: PHP worker wrote a new PHP file

severity
medium
confidence
55/100
generated
14 Nov 2026

A PHP worker created or renamed a .php / .phtml / .phar file. After remote code execution the usual next step is a web shell in the web root so access survives the patch. Not specific to one bug: it fires on code execution through the PHP web stack by any route. Attached to the 11 CVEs in this stack that skopnix reported in the last 30 days, newest CVE-2026-119977, CVE-2026-116606, CVE-2026-114625.

False-positive notes

Needs a PHP worker (php-fpm, php-cgi, lsphp, mod_php Apache) as the writing process and a PHP-executable extension. Template caches and CMS updates write PHP files on purpose; the rule excludes the common cache folders (cache, compiled, templates_c, twig, storage/framework/views, wp-content/upgrade) but expect update days to be loud. Hunt, then baseline per site.

References

Download .yml
title: 'Skopnix - PHP web stack: PHP worker wrote a new PHP file'id: bc20d3fe-b315-5791-b597-be09fbb30de7status: experimentaldescription: 'A PHP worker created or renamed a .php / .phtml / .phar file. After remote code execution the usual next step is a web shell in the web root so access survives the patch. Not specific to one bug: it fires on code execution through the PHP web stack by any route. Attached to the 11 CVEs in this stack that skopnix reported in the last 30 days, newest CVE-2026-119977, CVE-2026-116606, CVE-2026-114625.'references:  - https://skopnix.com/cve/CVE-2026-119977  - https://skopnix.com/cve/CVE-2026-116606  - https://skopnix.com/cve/CVE-2026-114625  - https://skopnix.com/cve/CVE-2026-111560  - https://skopnix.com/cve/CVE-2026-110447  - https://skopnix.com/cve/CVE-2026-109619  - https://skopnix.com/cve/CVE-2026-109618  - https://skopnix.com/cve/CVE-2026-104736  - https://skopnix.com/cve/CVE-2026-103849  - https://skopnix.com/cve/CVE-2026-102764  - https://skopnix.com/cve/CVE-2026-48356author: skopnixdate: '2026-11-14'tags:  - attack.execution  - attack.t1505.003  - cve.2026-119977  - cve.2026-116606  - cve.2026-114625  - cve.2026-111560  - cve.2026-110447  - cve.2026-109619  - cve.2026-109618  - cve.2026-104736  - cve.2026-103849  - cve.2026-102764  - cve.2026-48356logsource:  category: file_eventdetection:  selection_writer:    Image|re|i: '[/\\](php-fpm[0-9.]*|php-cgi[0-9.]*(\.exe)?|lsphp[0-9]*|frankenphp|apache2|httpd(\.exe)?)$'  selection_file:    TargetFilename|endswith:      - .php      - .phtml      - .phar      - .php5      - .php7  filter_caches:    TargetFilename|contains:      - /cache/      - /compiled/      - /templates_c/      - /twig/      - /storage/framework/views/      - /wp-content/upgrade/      - \cache\  condition: selection_writer and selection_file and not filter_cachesfalsepositives:  - CMS core / plugin / theme updates and cache compilers (WordPress, Joomla, Drupal, Laravel view cache, Smarty, Twig)  - Composer runs under PHP-FPM by some deployment toolslevel: medium

skopnix-sigma-cve-stack-php-worker-writes-php-f7c18264.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.