Loading vulnerability…
Bolt CMS 5.1.12 and earlier contains a vulnerability that allows an authenticated user with ROLE_EDITOR privileges to upload a malicious file and then rename it in a way that results in remote code execution. Based on the provided content, the issue is exploitable through the application's file handling workflow, specifically the combination of upload capability and subsequent rename operation available to an editor-level user.
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 proof-of-concept exploit for CVE-2022-36532, a vulnerability in Bolt CMS versions 5.1.12 and below. The exploit is implemented in a single Python script (CVE-2022-36532.py) and requires valid credentials for a user with at least EDITOR_ROLE permissions. The script automates the process of logging into the Bolt CMS instance, obtaining necessary CSRF tokens, uploading a PHP payload disguised as a .txt file, renaming it to .php, and then executing it to demonstrate remote code execution (RCE). The payload simply outputs the result of 7*7 (49) to confirm code execution. The README provides usage instructions and context. The exploit targets network-accessible Bolt CMS instances and interacts with several specific endpoints related to authentication and file management. No framework is used; the exploit is a standalone proof-of-concept.
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.