Skip to content
skopnix
← Cortex XDR detections

Cortex XDR · CVE exploitation

PHP web stack: Web server wrote a search-engine site-verification file

Correlation
set the rule's MITRE tactic to TA0002 and technique to T1491.002
severity
medium
confidence
60/100
generated
14 Nov 2026

A PHP worker, a shell or a download tool (wget, curl) created a Google (googleXXXXXXXXXXXXXXXX.html), Bing (BingSiteAuth.xml) or Yandex verification file. Gambling and pharma SEO-spam crews verify a hacked site in the search console so their hidden pages get indexed fast (often fetched with wget from the crew's own server); owners normally upload these files by SFTP or verify by DNS or a meta tag. 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, 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.

References

Download .xql
dataset = xdr_data| filter event_type = ENUM.FILE and (event_sub_type = ENUM.FILE_CREATE_NEW or event_sub_type = ENUM.FILE_WRITE or event_sub_type = ENUM.FILE_RENAME)| filter (lowercase(actor_process_image_name) ~= "^(php-fpm|php-cgi|lsphp)[0-9.]*(.exe)?$" or lowercase(actor_process_image_name) in ("frankenphp", "apache2", "httpd", "httpd.exe", "wget", "curl", "sh", "bash", "dash", "busybox")) and lowercase(action_file_name) ~= "^(google[0-9a-f]{16}[.]html|bingsiteauth[.]xml|yandex_[0-9a-f]{16}[.]html)$"| fields _time, agent_hostname, actor_effective_username, actor_process_image_name, actor_process_command_line, action_file_path, action_file_sha256, causality_actor_process_image_name| sort desc _time

skopnix-cortex-cve-stack-php-seo-verification-file-65e934d2.xql

How to deploy on Cortex 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.