# CVE-2007-4649: Privilege escalation in n/a

> Local attackers can escalate privileges by replacing application files due to weak directory permissions in MicroWorld eScan products.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Aug 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-pff6-h554-gmw5

## What is CVE-2007-4649?

CVE-2007-4649 is a high-severity vulnerability in n/a, published on 31 Aug 2007. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

MicroWorld eScan Virus Control 9.0.722.1, Anti-Virus 9.0.722.1, and Internet Security 9.0.722.1 use weak permissions (Everyone:Full Control) for their installation directory trees, which allows local users to gain privileges by replacing application files, as demonstrated by traysser.exe.

Weakness: CWE-264

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

It affects 3 products.


Products: Microworld Technologies Escan Anti-Virus, Microworld Technologies Escan Internet Security, Microworld Technologies Escan Virus Control.

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

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

## Is CVE-2007-4649 being exploited?

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

Public exploit code:

- Microworld eScan (Multiple Products) - Local Privilege Escalation (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-4649 is a high-severity vulnerability in n/a, published on 31 Aug 2007. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-4649 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-4649/ (Markdown: https://insights.sbomify.com/CVE-2007-4649/index.md)
```

## Sources

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

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