Loading vulnerability…
CVE-2026-11912 affects the Simple File List plugin for WordPress. In all versions up to and including 6.3.7, the plugin is vulnerable to arbitrary file modification because of insufficient authorization checks. According to the provided content, the vulnerable logic improperly relies on an is_admin() check that unconditionally short-circuits the access-control guard before the AllowFrontManage setting is evaluated. As a result, unauthenticated attackers can reach functionality intended to be restricted and use it to modify or delete files on the server.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
Repository contains a single Python exploit/scanner and a README. The main file, CVE-2026-11912.py, is a multithreaded mass scanner for CVE-2026-11912 affecting the Simple File List WordPress plugin <= 6.3.7. It uses requests.Session with TLS verification disabled, reads a list of targets, creates a timestamped results directory, and scans targets concurrently. The exploit workflow is: obtain eeSFL_ActionNonce from several sources (/file-list/, /wp-admin/admin-ajax.php, page source, or linked JavaScript), then brute-force eeSFL_ID values from 1 to 25 while sending POST requests to /wp-admin/admin-ajax.php with action simplefilelist_edit_job. It attempts file actions against traversal paths including wp-config.php, .htaccess, and /etc/passwd, and marks a target vulnerable when expected indicators appear in the response. The README documents the vulnerability as missing authorization for unauthenticated file modification, provides manual curl-based exploitation for delete and rename operations, and highlights path traversal leading to deletion of wp-config.php. Overall, this is a real exploit-oriented scanner rather than a pure detector: it actively performs file-operation requests to validate arbitrary file modification/deletion capability on vulnerable WordPress installations.
3 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.