Loading vulnerability…
PolarBear CMS 2.5 contains a vulnerability in upload.php that allows an attacker to upload arbitrary PHP files. This can be exploited to execute arbitrary code on the server, as the application does not properly validate or restrict the type of files that can be uploaded.
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 (polarcms_upload_exec.rb) that exploits a file upload vulnerability (CVE-2013-0803) in PolarBear CMS. The exploit abuses the upload.php endpoint in the /includes/jquery.uploadify/ directory, which allows unauthenticated file uploads to a temporary directory. The module uploads a PHP payload (generated by Metasploit) and then executes it, resulting in remote code execution on the target server. The exploit is configurable via TARGETURI and UPLOADDIR options, allowing adaptation to different installation paths. The code is written in Ruby and leverages Metasploit's HttpClient and PhpEXE mixins for HTTP requests and payload generation. The main attack vector is network-based, targeting a web application endpoint. The repository is weaponized, as it is a fully functional Metasploit exploit module capable of delivering arbitrary PHP payloads.
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.