T1491.002
T1491.002 on attack.mitre.org ↗
ATT&CK technique
- 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
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.