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

> Authenticated users can escalate privileges and modify system tables by exploiting symlink handling in RENAME TABLE operations when specific directory options are used.

- **Severity:** High 7.1 (`AV:N/AC:H/Au:S/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Dec 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-34f4-qcwh-g2jj

## What is CVE-2007-5969?

CVE-2007-5969 is a high-severity vulnerability in n/a, published on 10 Dec 2007. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

MySQL Community Server 5.0.x before 5.0.51, Enterprise Server 5.0.x before 5.0.52, Server 5.1.x before 5.1.23, and Server 6.0.x before 6.0.4, when a table relies on symlinks created through explicit DATA DIRECTORY and INDEX DIRECTORY options, allows remote authenticated users to overwrite system table information and gain privileges via a RENAME TABLE statement that changes the symlink to point to an existing file.

Weakness: CWE-264

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

It affects 3 products.


Products: Mysql Community Server, Mysql Mysql Enterprise Server, Mysql Mysql Server.

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

Upgrade to a fixed version.

## Is CVE-2007-5969 being exploited?

There is no known exploitation of CVE-2007-5969 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2007-3780](https://insights.sbomify.com/CVE-2007-3780/): Denial of service in n/a (medium 5.0)
- [CVE-2007-3781](https://insights.sbomify.com/CVE-2007-3781/): Missing authorization in n/a (medium 4.0)
- [CVE-2007-3782](https://insights.sbomify.com/CVE-2007-3782/): Privilege escalation in n/a (low 3.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-5969 is a high-severity vulnerability in n/a, published on 10 Dec 2007. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-5969 in the wild and no public exploit code.

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

## Sources

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

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