Loading vulnerability…
MobileCartly 1.0 contains an arbitrary file creation vulnerability in its page-saving functionality. The application passes attacker-controlled filename and content input to file_put_contents() without authentication or authorization checks, enabling unauthenticated requests to create attacker-chosen files in writable server locations. This can be leveraged to achieve remote code execution.
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/multi/http/mobilecartly_upload_exec.rb) that exploits an arbitrary file creation vulnerability in MobileCartly 1.0 (CVE-2012-10044). The exploit leverages the /includes/savepage.php endpoint, which allows unauthenticated users to write arbitrary files to the server due to missing permission checks. The module uploads a PHP payload to the /pages directory and then executes it by sending a request to the newly created PHP file. The exploit supports both PHP and Linux x86 payloads, making it versatile for different attack scenarios. The code is written in Ruby and follows the standard Metasploit module structure, including check and exploit methods. The main attack vector is network-based, requiring HTTP access to the vulnerable endpoints. The module is weaponized, allowing for customizable payloads and automated exploitation through the Metasploit framework.
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.