CVE-2012-10038 is an unauthenticated arbitrary file upload vulnerability in Auxilium RateMyPet, specifically in the upload_banners.php component. The banner upload functionality does not properly validate uploaded file types and does not enforce authentication before accepting uploads. As a result, a remote attacker can upload a malicious PHP file instead of a legitimate banner image. Because the uploaded file is stored in the web-accessible /banners/ directory, the attacker can then request the file directly over HTTP and cause the server to execute the PHP code, leading to 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 (auxilium_upload_exec.rb) that exploits an arbitrary file upload vulnerability in the Auxilium RateMyPet application (CVE-2012-10038). The exploit abuses the admin/sitebanners/upload_banners.php endpoint to upload a PHP payload to the server's banners directory, then accesses the uploaded file to trigger remote code execution. The module supports both PHP and Linux x86 payloads, leveraging Metasploit's payload generation and handler mechanisms. The code is written in Ruby and follows standard Metasploit module structure, with clear separation of initialization, vulnerability checking, payload upload, and exploitation logic. The main fingerprintable endpoints are the vulnerable upload script and the location where the payload is executed. This exploit 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.