Loading vulnerability…
CVE-2022-26352 is a critical vulnerability in dotCMS versions 3.0 through 22.02, specifically in the ContentResource API. The flaw allows attackers to upload files with unsanitized filenames via crafted multipart form requests, enabling directory traversal and saving files outside the intended storage location. If anonymous content creation is enabled, unauthenticated attackers can upload executable files (such as .jsp), leading to remote code execution. This vulnerability is classified as CWE-434 (Unrestricted Upload of File with Dangerous Type) and has a CVSS v3.1 base score of 9.8. Public exploit code is available, and the vulnerability is actively exploited in the wild, including by North Korean threat actors such as H0lyGh0st.
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 (dotcms_file_upload_rce.rb) that exploits CVE-2022-26352, a remote code execution vulnerability in dotCMS. The exploit leverages improper sanitization of filenames in the dotCMS content API (/api/content/), allowing an attacker to upload a malicious JSP file outside the intended temp directory and into the web root. The module uploads a JSP payload (default: java/jsp_shell_reverse_tcp) and then triggers its execution via an HTTP GET request, resulting in arbitrary code execution on the target server. The exploit targets both Linux and Windows platforms running dotCMS and is fully weaponized, allowing for customizable payloads within the Metasploit framework. The main attack vector is network-based, requiring access to the dotCMS content API endpoint. The repository is structured as a typical Metasploit module, with all logic contained in a single Ruby file.
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.
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.