Loading vulnerability…
AutoSec Tools V-CMS 1.0 contains an unrestricted file upload vulnerability in includes/inline_image_upload.php. Remote attackers can upload files with executable extensions to the temp/ directory and subsequently execute arbitrary code by directly accessing the uploaded file. The vulnerability is due to insufficient validation of uploaded file types and extensions.
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 contains a single Metasploit module (modules/exploits/linux/http/vcms_upload.rb) that exploits an unauthenticated file upload vulnerability in V-CMS (CVE-2011-4828). The exploit targets the inline_image_upload.php endpoint, which fails to properly validate uploaded file types, allowing attackers to upload and execute arbitrary PHP code. The module first uploads a PHP payload disguised as an image, then triggers its execution by sending a GET request to the uploaded file in the /temp/ directory. The exploit is weaponized, supporting customizable Metasploit payloads for remote code execution. The code is written in Ruby and leverages Metasploit's HttpClient and PhpEXE mixins. The main endpoints involved are /vcms/includes/inline_image_upload.php for uploading and /vcms/temp/<payload_name>.php for execution. The exploit is effective against V-CMS versions 1.0 and 1.1 on Linux platforms.
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.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
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.