# CVE-2019-12809: Code injection in YES24 PC VIEWER

> Remote attackers can execute arbitrary code by manipulating arguments in the YES24ViewerX ActiveX control, requiring users to update the software.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Aug 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-992x-5j6f-hjqq

## What is CVE-2019-12809?

CVE-2019-12809 is a high-severity code injection vulnerability in YES24 PC VIEWER, published on 15 Aug 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Yes24ViewerX ActiveX Control 1.0.327.50126 and earlier versions contains a vulnerability that could allow remote attackers to download and execute arbitrary files by setting the arguments to the ActiveX method. This can be leveraged for code execution.

Weakness: CWE-494 (Download of Code Without Integrity Check)

## Which versions are affected by CVE-2019-12809?

It affects 1 product.


Products: Yes24 Viewer Activex.

## How do I fix CVE-2019-12809?

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

## Is CVE-2019-12809 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-12809 and fix it if it is affected.

What it is: CVE-2019-12809 is a high-severity code injection vulnerability in YES24 PC VIEWER, published on 15 Aug 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-12809 in the wild and no public exploit code.

Affected product: YES24 PC VIEWER. 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-2019-12809/ (Markdown: https://insights.sbomify.com/CVE-2019-12809/index.md)
```

## Sources

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

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