# CVE-2007-4982: Path traversal in n/a

> Remote attackers can overwrite arbitrary files via path traversal in the QRCode ActiveX control, requiring user interaction to trigger the vulnerable methods.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **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:** 19 Sep 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-p68h-7w45-x23q

## What is CVE-2007-4982?

CVE-2007-4982 is a critical path traversal vulnerability in n/a, published on 19 Sep 2007. 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

Multiple absolute path traversal vulnerabilities in the MW6QRCode.QRCode.1 ActiveX control in MW6QRCode.dll in MW6 Technologies QRCode ActiveX 3.0.0.1 and earlier allow remote attackers to create or overwrite arbitrary files via a full pathname in the argument to the (1) SaveAsBMP or (2) SaveAsWMF method.  NOTE: some of these details are obtained from third party information.

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

## Which versions are affected by CVE-2007-4982?

It affects 1 product.


Products: Mw6 Technologies Qrcode Activex.

## How do I fix CVE-2007-4982?

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

## Is CVE-2007-4982 being exploited?

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

Public exploit code:

- MW6 Technologies QRCode ActiveX 3.0 - Remote File Overwrite (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-4982 and fix it if it is affected.

What it is: CVE-2007-4982 is a critical path traversal vulnerability in n/a, published on 19 Sep 2007. 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-2007-4982 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-2007-4982/ (Markdown: https://insights.sbomify.com/CVE-2007-4982/index.md)
```

## Sources

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

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