EGallery 1.2 contains an unauthenticated arbitrary file upload vulnerability in uploadify.php. The application does not validate uploaded file types or enforce authentication, allowing an attacker to upload malicious PHP files to a web-accessible EGallery directory and execute them in the web-server context.
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 (egallery_upload_exec.rb) that exploits an unauthenticated file upload vulnerability in EGallery 1.2 (CVE-2012-10052). The exploit abuses the uploadify.php script to upload a malicious PHP payload to the egallery/ directory. Once uploaded, the payload is executed by sending an HTTP GET request to the uploaded file, resulting in remote code execution. The module is written in Ruby and leverages Metasploit's HttpClient mixin. The only required configuration is the TARGETURI option, which specifies the base path to the EGallery installation. The exploit is operational and provides the attacker with the ability to execute arbitrary PHP code on the target server. The main fingerprintable endpoints are /egallery/uploadify.php (for upload) and the resulting /egallery/<payload>.php (for execution).
4 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.