Loading vulnerability…
CVE-2026-67206 is a remote code execution vulnerability affecting Wolf CMS through version 0.8.3.1. The flaw resides in FileManagerController, where the create_file() and save() functions fail to enforce proper file extension validation. An authenticated attacker with the file_manager_mkfile capability can create arbitrary PHP files containing attacker-controlled code in the web-accessible FILES_DIR directory. Because those files can then be requested over HTTP, the attacker can cause the server to execute the uploaded PHP code.
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 (1 hidden).
This repository is a small standalone Python proof-of-concept exploit for CVE-2026-67206 affecting Wolf CMS through 0.8.3.1. The repo contains four files: a README with vulnerability description and usage instructions, exploit.py containing the exploit logic, requirements.txt listing requests and BeautifulSoup dependencies, and a license file. The exploit automates an authenticated arbitrary file write leading to remote code execution. Its workflow is: authenticate to the Wolf CMS admin interface using supplied credentials, request File Manager pages to scrape CSRF tokens from HTML forms, create a new file named shell.php via the vulnerable create_file functionality, then save PHP code into that file via the save functionality. The payload is a minimal PHP web shell using system($_GET['cmd']), after which the script immediately tests execution by requesting /public/shell.php?cmd=whoami. Main capabilities: authenticated login, CSRF token extraction, arbitrary file creation through the admin File Manager, arbitrary PHP content write, web shell deployment, and command execution verification. This is not a scanner or detector; it is an actual exploit with a hardcoded payload, making it operational rather than a mere PoC. There is no framework integration, no obfuscation, and no advanced post-exploitation logic beyond dropping and invoking the shell.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.