# CVE-2024-13959: Link Following Local Privilege Escalation Vulnerability in AVG TuneUp 24.2.16593.9844

> Local attackers can escalate privileges to SYSTEM and execute arbitrary code by exploiting a link following vulnerability in the TuneUp service.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 9 May 2025
- **Updated:** 9 May 2025
- **Also known as:** GHSA-3vr2-w427-fcqp

## What is CVE-2024-13959?

CVE-2024-13959 is a high-severity vulnerability in AVG TuneUp, published on 9 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Link Following Local Privilege Escalation Vulnerability in TuneupSvc.exe in AVG TuneUp 24.2.16593.9844 on Windows allows local attackers to escalate privileges and execute arbitrary code in the context of SYSTEM via creating a symbolic link and leveraging the service to delete a directory

Weakness: CWE-59 (Improper Link Resolution Before File Access)

## Which versions are affected by CVE-2024-13959?


## How do I fix CVE-2024-13959?

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

## Is CVE-2024-13959 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-13959 and fix it if it is affected.

What it is: CVE-2024-13959 is a high-severity vulnerability in AVG TuneUp, published on 9 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-13959 in the wild and no public exploit code.

Affected product: AVG TuneUp. 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-2024-13959/ (Markdown: https://insights.sbomify.com/CVE-2024-13959/index.md)
```

## Sources

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

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