Skip to content
skopnix
← IBM QRadar detections

IBM QRadar · CVE exploitation

PHP web stack: WordPress file-manager plugin used over the web

severity
high
confidence
70/100
generated
14 Nov 2026

A request to the WP File Manager screen or its elFinder connector (action=mk_file_folder_manager: upload, extract, edit, rename) or one that activates the plugin. After a stolen-password login this is how an attacker uploads and unpacks a web-shell archive. 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 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.

References

SELECT sourceip, destinationip, destinationport, QIDNAME(qid) AS event, LOGSOURCENAME(logsourceid) AS log_source, "URL"FROM eventsWHERE (("URL" ILIKE '%page=wp_file_manager%' OR "URL" ILIKE '%action=mk_file_folder_manager%' OR "URL" ILIKE '%plugin=wp-file-manager%'))AND LOGSOURCETYPENAME(devicetype) IN ('Apache HTTP Server', 'Microsoft IIS', 'F5 Networks BIG-IP ASM', 'Squid Web Proxy', 'Blue Coat SG', 'Zscaler Nanolog Streaming Service', 'Palo Alto PA Series', 'Fortinet FortiGate Security Gateway', 'Imperva SecureSphere', 'Citrix NetScaler', 'Akamai KONA')LAST 7 DAYS

skopnix-qradar-cve-stack-php-file-manager-web-actions-e1416e9d.aql

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