CVE-2025-24885
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedpwn.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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidencepwn.college fails to enforce proper access controls on custom dojo page rendering, allowing unprivileged users to create and store malicious content. This missing authorization check on the page rendering functionality enables stored Cross-Site Scripting (XSS) attacks where malicious scripts are persisted and executed when other users view the compromised pages.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify pwn.college installation is accessibleConfirm the pwn.college web application is running and reachable at its expected URLAffected if The application is running and accessible to unprivileged users without authentication requirements for page creation.
-
Identify available user roles and privilegesLog into the application and enumerate the user role hierarchy - check if there are distinct privilege levels (e.g., student, instructor, admin) and whether role assignment is publicly visible or configurableAffected if The system defines multiple roles but does not restrict custom dojo page creation to privileged roles only.
-
Test page creation access for unprivileged accountsCreate a standard (non-admin) user account and attempt to create or modify a custom dojo page using the page rendering functionalityAffected if Unprivileged users can successfully create, store, or modify page content that is persisted and rendered to other users.
-
Inspect stored page content for lack of sanitizationAfter creating a test page with script tags or HTML content, retrieve the page and examine the stored response to see if content is rendered as-is without sanitization or encodingAffected if The stored page content is rendered directly to other users without input sanitization, enabling stored XSS.
-
Review application logs for authorization checksExamine server-side logs or code for presence of role-based access control (RBAC) checks before executing page rendering logicAffected if No authorization verification occurs before the page rendering function executes custom dojo page content.
A user is affected if unprivileged accounts can create or modify custom dojo pages that get stored and rendered to other users without any authorization or input sanitization checks.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement role-based access control (RBAC) to verify user privileges before rendering custom dojo pages, ensuring only authorized users can create or modify page content that gets stored and rendered to other users.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24885 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-24885 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data