# CVE-2025-24885: pwn.college has a XSS on dojo pages

> Attackers can inject malicious scripts into dojo pages due to missing access controls, potentially compromising user sessions.

- **Severity:** High 7.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 30 Jan 2025
- **Updated:** 31 Jan 2025
- **Also known as:** GHSA-8m79-rmhw-rg84

## What is CVE-2025-24885?

CVE-2025-24885 is a high-severity cross-site scripting vulnerability in pwncollege dojo, published on 30 Jan 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

pwn.college is an education platform to learn about, and practice, core cybersecurity concepts in a hands-on fashion. Missing access control on rendering custom (unprivileged) dojo pages causes ability for users to create stored XSS.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation), CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2025-24885 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-24885 is a high-severity cross-site scripting vulnerability in pwncollege dojo, published on 30 Jan 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-24885 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-24885/ (Markdown: https://insights.sbomify.com/CVE-2025-24885/index.md)
```

## Sources

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

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