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

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

- **Severity:** Critical 9.3 (`AV:N/AC:M/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:** 5 Nov 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-v4p8-cpq3-f35v

## What is CVE-2007-5826?

CVE-2007-5826 is a critical path traversal vulnerability in n/a, published on 5 Nov 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

Absolute path traversal vulnerability in the EDraw Flowchart ActiveX control in EDImage.ocx 2.0.2005.1104 allows remote attackers to create or overwrite arbitrary files with arbitrary contents via a full pathname in the second argument to the HttpDownloadFile method, a different product than CVE-2007-4420.

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

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

It affects 1 product.


Products: Edraw Flowchart Activex.

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

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

## Is CVE-2007-5826 being exploited?

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

Public exploit code:

- EDraw Flowchart ActiveX Control 2.0 - Insecure Method (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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