CVE-2022-26352 — core
CRITICALCVE-2022-26352 is a critical-severity (CVSS 9.8) remote code execution vulnerability. It is in CISA's Known Exploited Vulnerabilities catalog (added 2022-08-25) and has been used in ransomware campaigns — treat it as actively exploited and patch now. No vendor fix is recorded yet; mitigation options are listed below.
Exploitation Status
Actively exploited in the wild
- Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2022-08-25 — including use in ransomware campaigns. Federal agencies were required to remediate by 2022-09-15.
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2022-26352.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2022-26352 by exploitation likelihood (EPSS) against impact (CVSS). In the shaded patch-first corner (EPSS 50%+, CVSS 7.0+).
Where this sits among everything scored
Of 395,249 CVEs with a current EPSS score, this one falls in the ≥ 90% band (highlighted). Counts from FIRST.org, log-scaled.
Description
An issue was discovered in the ContentResource API in dotCMS 3.0 through 22.02. Attackers can craft a multipart form request to post a file whose filename is not initially sanitized. This allows directory traversal, in which the file is saved outside of the intended storage location. If anonymous content creation is enabled, this allows an unauthenticated attacker to upload an executable file, such as a .jsp file, that can lead to remote code execution.
Affected Products
dotcmsdotcmsResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
An issue was discovered in the ContentResource API in dotCMS 3.0 through…
An issue was discovered in the ContentResource API in dotCMS 3.0 through…
An issue was discovered in the ContentResource API in dotCMS 3.0 through…
Detection & mitigation playbook
VulnerabilityDetect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Remediation status
No fixed release is recorded for CVE-2022-26352 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.
Mitigate without a patch
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.
How to detect CVE-2022-26352
A community-maintained Nuclei template exists for this CVE. You can scan for it directly:
nuclei -id cve-2022-26352 -u https://target- Template
- DotCMS - Arbitrary File Upload
- Severity
- critical
- Impact
- Successful exploitation of this vulnerability can lead to remote code execution, compromising the confidentiality, integrity, and availability of the affected system.
- Remediation
- Apply the latest security patches or updates provided by the vendor to fix this vulnerability.
Template by ProjectDiscovery nuclei-templates (h1ei1), MIT licensed. View the full template. Scan only systems you are authorised to test.
Frequently Asked Questions
Is CVE-2022-26352 in your dependencies?
Find it across , including transitive dependencies.