Loading vulnerability…
CVE-2026-37068 is an arbitrary file-write vulnerability in Veno File Manager Project 4.4.9. The translation-update administrative functionality insufficiently restricts the destination of written content, allowing a super administrator to use a specially crafted POST request to overwrite arbitrary PHP files in the application.
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.
This repository is a minimal proof-of-concept exploit for CVE-2026-37068 affecting Veno File Manager 4.4.9. It contains two files: a Bash exploit script (PoC.sh) and a short README describing the issue. The exploit is not part of a larger framework. The main capability is an authenticated arbitrary file overwrite/write primitive available to a super administrator. The script takes four arguments: the VFM session cookie name, the cookie value, a target file path relative to the application root (without extension), and the base URL of the VFM installation. It then sends a POST request with the authenticated cookie to /vfm-admin/index.php?section=translations&action=update and sets thenewlang to a traversal sequence (../../../<target path>). This indicates the vulnerable code likely uses the language name/path unsafely when writing translation files, enabling traversal outside the intended directory. Operationally, the script uses curl to issue a single POST request and suppresses output. After execution, it prints the expected resulting PHP file location as <base URL>/<target>.php. The exploit does not include a secondary payload such as webshell content, reverse shell logic, or code execution automation; instead, it demonstrates the file-write/overwrite capability that could be chained into remote code execution if the attacker can cause executable PHP content to be written to a web-accessible location. Repository structure is extremely small and purpose-built: README.md documents the vulnerability and affected endpoint, while PoC.sh is the sole executable artifact and likely the only entry point. No detection logic, scanning features, persistence, or post-exploitation modules are present.
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.
1 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.