# CVE-2013-6127: Path traversal in n/a

> Remote attackers can exploit an ActiveX control to overwrite arbitrary files and execute code via directory traversal, requiring user interaction.

- **Severity:** Medium 5.8 (`AV:N/AC:M/Au:N/C:N/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:** 25 Oct 2013
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-wg24-f677-c248

## What is CVE-2013-6127?

CVE-2013-6127 is a medium-severity path traversal vulnerability in n/a, published on 25 Oct 2013. 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

The SUPERGRIDLib.SuperGrid ActiveX control in SuperGrid.ocx before 65.30.30000.10002 in WellinTech KingView before 6.53 does not properly restrict ReplaceDBFile method calls, which allows remote attackers to create or overwrite arbitrary files, and subsequently execute arbitrary programs, via the two pathname arguments, as demonstrated by a directory traversal attack.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Wellintech Kingview.

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

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

## Is CVE-2013-6127 being exploited?

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

Public exploit code:

- KingView 6.53 - 'SuperGrid' Insecure ActiveX Control (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2012-4711](https://insights.sbomify.com/CVE-2012-4711/): Memory corruption in n/a (critical 10.0)
- [CVE-2012-1830](https://insights.sbomify.com/CVE-2012-1830/): Memory corruption in n/a (critical 10.0)
- [CVE-2012-1831](https://insights.sbomify.com/CVE-2012-1831/): Memory corruption in n/a (critical 10.0)
- [CVE-2012-1832](https://insights.sbomify.com/CVE-2012-1832/): Memory corruption in n/a (critical 10.0)
- [CVE-2011-4536](https://insights.sbomify.com/CVE-2011-4536/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-6127 is a medium-severity path traversal vulnerability in n/a, published on 25 Oct 2013. 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-6127 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-6127/ (Markdown: https://insights.sbomify.com/CVE-2013-6127/index.md)
```

## Sources

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

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