BiggiDroid Simple PHP CMS 1.0 contains an unrestricted file upload vulnerability in /admin/editsite.php. By manipulating the 'image' parameter, an attacker can upload arbitrary files without effective server-side restrictions on type/extension/content. The issue is remotely exploitable and a public exploit is available; depending on how uploaded files are stored and handled by the web server, this may enable webshell placement and subsequent 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 documents a critical arbitrary file upload vulnerability (CVE-2025-15495) in BiggiDroid's Simple PHP Blog CMS. The exploit allows an authenticated attacker to upload a malicious PHP file (web shell) via the admin panel's 'Update Site Logo' functionality. The uploaded file is stored in a web-accessible directory without any extension or MIME type validation, enabling remote code execution by accessing the file directly via HTTP. The proof of concept demonstrates uploading a PHP shell and executing OS commands through the 'cmd' parameter. The repository consists of a detailed README.md with vulnerability analysis, PoC steps, and screenshots, and a placeholder image file. No automated exploit script is provided, but the README includes the full web shell payload and exploitation steps. The attack vector is network-based, targeting the web application's file upload mechanism. The main fingerprintable endpoints are the upload directory and the URL where the shell is accessed. The exploit is a proof of concept and not weaponized.
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.
2 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.