# CVE-2023-27770: Command injection in n/a

> A remote attacker can execute arbitrary commands via the Edraw Max installer file, requiring users to update the application.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 4 Apr 2023
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-46pm-cwjr-9r9x

## What is CVE-2023-27770?

CVE-2023-27770 is a high-severity command injection vulnerability in n/a, published on 4 Apr 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

An issue found in Wondershare Technology Co.,Ltd Edraw-max v.12.0.4 allows a remote attacker to execute arbitrary commands via the edraw-max_setup_full5371.exe file.

Weakness: CWE-426 (Untrusted Search Path), CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2023-27770?

It affects 1 product.


Products: Wondershare Edraw-Max.

## How do I fix CVE-2023-27770?

No fix has been published for CVE-2023-27770 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-27770 being exploited?

There is no known exploitation of CVE-2023-27770 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-27770 and fix it if it is affected.

What it is: CVE-2023-27770 is a high-severity command injection vulnerability in n/a, published on 4 Apr 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-27770 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-27770/ (Markdown: https://insights.sbomify.com/CVE-2023-27770/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-27770
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-27770
- OSV: https://osv.dev/vulnerability/CVE-2023-27770

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-27770/
Summaries are generated and may contain mistakes; the official description above is the record.