CVE-2026-109619
Linked CVE
- PHP web stack: PHP worker built an ALFA-style CGI shell folderSIGXQLT1059.004T1505.003conf 80CVE exploitation, high
Needs a PHP worker as the writer and "cgiapi" in the path or an .alfa extension. A copy renamed without either marker is missed; worker-writes-php and worker-shell cover the rest of the chain.
CVE-2026-102764 · CVE-2026-103849 · CVE-2026-104736 · CVE-2026-109618 · CVE-2026-109619 · CVE-2026-110447 · CVE-2026-111560 · CVE-2026-114625 · CVE-2026-116606 · CVE-2026-119977 · CVE-2026-48356
- CVE-2026-109619 exploitation IP indicatorsSIGAQLXQLT1071conf 75CVE exploitation, high
2 indicators. Evidence: 2 listed by 2 or more independent non-scanner feed publishers. Listed by 6 independent sources in all. Newest feed sighting 2026-11-13, oldest 2026-10-28 (a live actor sweep accepts at most 90 days). Screened against reserved space, public known-good lists (CDN / cloud / scanners / top sites), internet-noise reputation when enriched, and sinkhole address lists. Re-validate against last_seen before blocking: infrastructure is re-assigned.
- PHP web stack: A download tool wrote a PHP file into a web rootSIGXQLT1105T1505.003conf 75CVE exploitation, high
Needs wget / curl / a shell as the writer, a PHP-executable extension and a web-root path (public_html, /var/www/, /srv/www/, htdocs, wp-content, wp-includes, wp-admin). Package managers (apt, dnf, composer), git checkouts and SFTP uploads are other writers and do not match.
CVE-2026-102764 · CVE-2026-103849 · CVE-2026-104736 · CVE-2026-109618 · CVE-2026-109619 · CVE-2026-110447 · CVE-2026-111560 · CVE-2026-114625 · CVE-2026-116606 · CVE-2026-119977 · CVE-2026-48356
- PHP web stack: A file-manager plugin was installed by the web serverSIGXQLT1105T1505.003conf 75CVE exploitation, high
Needs a PHP worker (php-fpm, php-cgi, lsphp, mod_php Apache) as the writing process and a path inside one of the named file-manager plugin folders or its wp-content/upgrade staging folder. Other plugins do not match. One install writes hundreds of files: group by host.
CVE-2026-102764 · CVE-2026-103849 · CVE-2026-104736 · CVE-2026-109618 · CVE-2026-109619 · CVE-2026-110447 · CVE-2026-111560 · CVE-2026-114625 · CVE-2026-116606 · CVE-2026-119977 · CVE-2026-48356
- PHP2Shell (CVE-2026-109618 / CVE-2026-109619): web request reads a PHP session fileSIGAQLXQLT1190conf 75CVE exploitation, high
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.
- PHP web stack: WordPress file-manager plugin used over the webSIGAQLXQLT1505.003conf 70CVE exploitation, high
Needs the plugin's own page or connector name in the URL (page=wp_file_manager, action=mk_file_folder_manager, plugin=wp-file-manager). Other plugins and ordinary wp-admin pages do not match. WP File Manager's connector carries action= in the query string, so it shows in access logs; check one request in your logs first.
CVE-2026-102764 · CVE-2026-103849 · CVE-2026-104736 · CVE-2026-109618 · CVE-2026-109619 · CVE-2026-110447 · CVE-2026-111560 · CVE-2026-114625 · CVE-2026-116606 · CVE-2026-119977 · CVE-2026-48356
- PHP web stack: PHP worker spawned a shell or download toolSIGAQLXQLT1059.003T1059.004T1190T1505.003conf 70CVE exploitation
Needs a PHP worker or mod_php Apache as the PARENT and a shell / interpreter / downloader as the child. PHP mail() (sh -c sendmail / msmtp / exim / postdrop) and Apache piped logging (rotatelogs, cronolog) are excluded. The PHP command-line binary is not a parent on purpose (cron jobs and artisan / wp-cli run it all day and it is not reachable from the network). Legitimate exec() calls in an application still match: hunt for a week and baseline them before alerting.
CVE-2026-102764 · CVE-2026-103849 · CVE-2026-104736 · CVE-2026-109618 · CVE-2026-109619 · CVE-2026-110447 · CVE-2026-111560 · CVE-2026-114625 · CVE-2026-116606 · CVE-2026-119977 · CVE-2026-48356
- PHP web stack: Web server wrote a search-engine site-verification fileSIGXQLT1491.002conf 60CVE exploitation
Needs a PHP worker, a shell or wget / curl as the writer and the exact verification file names (16 hex characters for Google and Yandex). An attacker who verifies by meta tag or DNS is missed; a file uploaded by SFTP is not one of these writers and does not match.
CVE-2026-102764 · CVE-2026-103849 · CVE-2026-104736 · CVE-2026-109618 · CVE-2026-109619 · CVE-2026-110447 · CVE-2026-111560 · CVE-2026-114625 · CVE-2026-116606 · CVE-2026-119977 · CVE-2026-48356
- PHP web stack: PHP worker wrote a new PHP fileSIGXQLT1505.003conf 55CVE exploitation
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.
CVE-2026-102764 · CVE-2026-103849 · CVE-2026-104736 · CVE-2026-109618 · CVE-2026-109619 · CVE-2026-110447 · CVE-2026-111560 · CVE-2026-114625 · CVE-2026-116606 · CVE-2026-119977 · CVE-2026-48356
- PHP2Shell (CVE-2026-109618 / CVE-2026-109619): PHP worker crashes (possible heap exploitation)AQLT1190conf 50CVE exploitation
Reads the raw syslog payload, so it needs php-fpm's error log or the kernel log forwarded (Linux OS log source). One crash means little; the AQL groups by server and keeps only hosts with 5 or more crashes in the window.
How to deploy
SIGSigma
- 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.
AQLIBM QRadar
- Step 1
- Create the reference set from its spec (Reference Data API, or Admin > Reference Set Management) and schedule the skopnix feed load.
- Step 2
- Paste the AQL into Log Activity > Advanced Search to hunt the last seven days.
- Step 3
- For alerting, build the CRE rule from the test stack shown and exclude your known-good building block.
- Check
- Custom properties ("URL Host", "URL", "File Hash", "Process CommandLine") come from your DSMs and content extensions; rename them if yours differ.
XQLCortex XDR
- Step 1
- Paste the XQL into Incident Response > Investigation > Query Builder > XQL Search.
- Step 2
- To alert, save it as a Correlation Rule and set the MITRE tactic and technique printed with the rule.
- Step 3
- Schedule it on the interval you hunt at; keep the fields stage for the alert's columns.
- Check
- CVE rules read PAN-OS URL logs (panw_ngfw_url_raw), which need the NGFW integration and, for HTTPS, decryption.