# CVE-2013-2827: Code injection in n/a

> Remote attackers can execute arbitrary code on client machines via a malicious ActiveX control in WellinTech KingSCADA products.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **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 Jan 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-mprw-5m59-x962

## What is CVE-2013-2827?

CVE-2013-2827 is a high-severity code injection vulnerability in n/a, published on 15 Jan 2014. 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

An unspecified ActiveX control in WellinTech KingSCADA before 3.1.2, KingAlarm&Event before 3.1, and KingGraphic before 3.1.2 allows remote attackers to download arbitrary DLL code onto a client machine and execute this code via the ProjectURL property value.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2013-2827?

It affects 3 products.


Products: Wellintech Kingalarm\&event, Wellintech Kinggraphic, Wellintech Kingscada.

## How do I fix CVE-2013-2827?

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

## Is CVE-2013-2827 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-2827 exists.

Public exploit code:

- KingScada kxClientDownload.ocx ActiveX Remote Code Execution (metasploit)
- KingScada - kxClientDownload.ocx ActiveX Remote Code Execution (Metasploit) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2013-2826](https://insights.sbomify.com/CVE-2013-2826/): Auth bypass in n/a (medium 6.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-2827 and fix it if it is affected.

What it is: CVE-2013-2827 is a high-severity code injection vulnerability in n/a, published on 15 Jan 2014. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-2827 exists.

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-2013-2827/ (Markdown: https://insights.sbomify.com/CVE-2013-2827/index.md)
```

## Sources

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

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