# CVE-2013-5701: Privilege escalation in n/a

> Local attackers can escalate privileges by placing a malicious DLL in the application directory of WatchGuard Server Center components.

- **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:** 3 Oct 2013
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-7w4c-hrjr-pvjp

## What is CVE-2013-5701?

CVE-2013-5701 is a high-severity vulnerability in n/a, published on 3 Oct 2013. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Multiple untrusted search path vulnerabilities in (1) Watchguard Log Collector (wlcollector.exe) and (2) Watchguard WebBlocker Server (wbserver.exe) in WatchGuard Server Center 11.7.4, 11.7.3, and possibly earlier allow local users to gain privileges via a Trojan horse wgpr.dll file in the application's bin directory.

Weakness: CWE-264

## Which versions are affected by CVE-2013-5701?

It affects 1 product.


Products: Watchguard Server Center.

## How do I fix CVE-2013-5701?

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

## Is CVE-2013-5701 being exploited?

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

Public exploit code:

- Watchguard Server Center - Local Privilege Escalation (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-5701 and fix it if it is affected.

What it is: CVE-2013-5701 is a high-severity vulnerability in n/a, published on 3 Oct 2013. 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-2013-5701 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-2013-5701/ (Markdown: https://insights.sbomify.com/CVE-2013-5701/index.md)
```

## Sources

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

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