Loading vulnerability…
In Bolt CMS versions prior to 2.2.5, the theme editor functionality fails to validate file extensions when renaming files. This allows an authenticated user to rename a file to an executable extension (such as .php), upload arbitrary code, and subsequently execute it by accessing the file directly.
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/bolt_file_upload.rb) that exploits an authenticated file upload vulnerability in Bolt CMS version 2.2.4 (CVE-2015-7309). The exploit requires valid user credentials and the theme folder name. It works by logging into the CMS, obtaining a CSRF token, uploading a PHP payload disguised as a PNG image to the theme folder, renaming the file to have a .php extension, and then executing it via a direct HTTP request. The module leverages Metasploit's payload system, allowing for customizable PHP payloads (such as reverse shells or Meterpreter sessions). The attack vector is network-based, targeting the web interface of Bolt CMS. The endpoints involved include authentication, file upload, file renaming, and payload execution URLs. The code is written in Ruby and is fully integrated into the Metasploit framework, making it a weaponized exploit.
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.