# CVE-2025-62376: pwn.college DOJO vulnerable to improper authentication in workspace endpoint allowing unauthorized Windows VM access

> Attackers can bypass authentication to access and modify data on other users' Windows VMs by supplying arbitrary user IDs and passwords.

- **Severity:** Critical 9.5 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:L/SC:H/SI:H/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Oct 2025
- **Updated:** 3 Dec 2025
- **Also known as:** GHSA-344w-77p7-gx2c

## What is CVE-2025-62376?

CVE-2025-62376 is a critical authentication bypass vulnerability in pwncollege dojo, published on 14 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

pwn.college DOJO is an education platform for learning cybersecurity. Prior to commit 467db0b9ea0d9a929dc89b41f6eb59f7cfc68bef, the /workspace endpoint contains an improper authentication vulnerability that allows an attacker to access any active Windows VM without proper authorization. The vulnerability occurs in the view_desktop function where the user is retrieved via a URL parameter without verifying that the requester has administrative privileges. An attacker can supply any user ID and arbitrary password in the request parameters to impersonate another user. When requesting a Windows desktop service, the function does not validate the supplied password before generating access credentials, allowing the attacker to obtain an iframe source URL that grants full access to the target user's Windows VM. This impacts all users with active Windows VMs, as an attacker can access and modify data on the Windows machine and in the home directory of the associated Linux machine via the Z: drive. This issue has been patched in commit 467db0b9ea0d9a929dc89b41f6eb59f7cfc68bef. No known workarounds exist.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2025-62376?


## How do I fix CVE-2025-62376?

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

## Is CVE-2025-62376 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-62376 and fix it if it is affected.

What it is: CVE-2025-62376 is a critical authentication bypass vulnerability in pwncollege dojo, published on 14 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-62376 exists.

Affected product: pwncollege dojo. 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-2025-62376/ (Markdown: https://insights.sbomify.com/CVE-2025-62376/index.md)
```

## Sources

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

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