CVE-2018-25443 json
Baidu UEditor 1.4.0-1.4.3.3 Unrestricted File Upload via controller.ashx
published 10h ago modified 9h ago also EUVD-2018-21964
- cvss
- 9.3
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no EPSS score yet
- public exploits
- 0
- none known
Summary
Baidu UEditor 1.4.0 through 1.4.3.3 contains an unrestricted file upload vulnerability in the catchimage action of /ueditor/net/controller.ashx that only validates the Content-Type header. Unauthenticated attackers can supply a source[] URL like x.jpg?.aspx to retain a malicious extension and write an executable .aspx file for remote code execution. Exploitation evidence was first observed by the Shadowserver Foundation on 2023-10-17.
Is CVE-2018-25443 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 FencerExploits and checks
- web.archive.org https://web.archive.org/web/20190612114715/https://www.freebuf.com/vuls/181814.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 9.3 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N |
| CNA | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Baidu UEditor
Classification
- Weakness
-
- CWE-434 Unrestricted Upload of File with Dangerous Type
References
-
web.archive.org
/web/20190612114715/https://www.freebuf.com/vuls/181814.html
technical-description, exploit
-
github.com
/fex-team/ueditor/blob/v1.4.3.3/net/App_Code/CrawlerHandler.cs
technical-description
-
github.com
/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/other/ueditor-file-upload.yaml
technical-description
-
vulncheck.com
/advisories/baidu-ueditor-1.4.0-1.4.3.3-unrestricted-file-upload-via-controller-ashx
third-party-advisory
Sources
- CVE List CVE-2018-25443
- NVD CVE-2018-25443
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.