CVE-2017-11466 json
Arbitrary file upload vulnerability in com/dotmarketing/servlets/AjaxFileUploadServlet.class in dotCMS 4.1.1 allows remote authenticated ad…
published 9y ago modified 4mo ago also EUVD-2017-3087
- cvss
- 7.2
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 7.7%
- EPSS 7.7% chance of exploitation in 30 days, percentile 94%
- public exploits
- 0
- none known
Summary
Arbitrary file upload vulnerability in com/dotmarketing/servlets/AjaxFileUploadServlet.class in dotCMS 4.1.1 allows remote authenticated administrators to upload .jsp files to arbitrary locations via directory traversal sequences in the fieldName parameter to servlets/ajax_file_upload. This results in arbitrary code execution by requesting the .jsp file at a /assets URI.
Patch / fix
- github.com/dotCMS/core/issues/12131 advisory
Is CVE-2017-11466 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
7.70% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- seclists.org http://seclists.org/fulldisclosure/2017/Jul/33 referenced PoC, tagged "exploit" by a source, unverified
- packetstormsecurity.com https://packetstormsecurity.com/files/143383/dotcms411-shell.txt referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.2 | CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 9.0 | AV:N/AC:L/Au:S/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-434 Unrestricted Upload of File with Dangerous Type
References
-
github.com
/dotCMS/core/issues/12131
issue-tracking, patch, third-party-advisory
-
seclists.org
/fulldisclosure/2017/Jul/33
exploit, mailing-list, third-party-advisory
-
packetstormsecurity.com
/files/143383/dotcms411-shell.txt
exploit, third-party-advisory, vdb-entry
Sources
- CVE List CVE-2017-11466
- NVD CVE-2017-11466
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.