CVE-2026-25117 in dojo
Summary
by MITRE • 01/30/2026
pwn.college DOJO is an education platform for learning cybersecurity. Prior to commit e33da14449a5abcff507e554f66e2141d6683b0a, missing sandboxing on `/workspace/*` routes allows challenge authors to inject arbitrary javascript which runs on the same origin as `http[:]//dojo[.]website`. This is a sandbox escape leading to arbitrary javascript execution as the dojo's origin. A challenge author can craft a page that executes any dangerous actions that the user could. Version e33da14449a5abcff507e554f66e2141d6683b0a patches the issue.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Analysis
by VulDB Data Team • 02/05/2026
The vulnerability identified as CVE-2026-25117 affects the pwn.college DOJO platform, an educational cybersecurity environment designed for teaching offensive security concepts. This platform hosts various challenges that users can attempt to complete, with challenge authors creating content that runs within the platform's infrastructure. The vulnerability stems from inadequate sandboxing mechanisms within the `/workspace/*` route handlers, which are intended to provide isolated environments for challenge execution. Prior to the fix implemented in commit e33da14449a5abcff507e554f66e2141d6683b0a, the platform failed to properly isolate challenge content from the main application's security boundaries.
The technical flaw manifests as a sandbox escape condition where challenge authors can inject arbitrary javascript code into the platform's execution environment. This occurs because the `/workspace/*` routes lack proper input validation and sanitization, allowing malicious code injection that executes within the same origin as the main dojo website at http[:]//dojo[.]website. The vulnerability represents a classic cross-site scripting issue that has been escalated to a sandbox escape scenario, as the injected code runs with the privileges and permissions of the dojo application itself. The same-origin policy, which normally protects web applications from malicious code execution, is effectively bypassed through this vulnerability.
The operational impact of this vulnerability is severe as it provides challenge authors with the capability to execute arbitrary javascript code with the full privileges of the dojo platform. This means that malicious actors could potentially access user data, perform unauthorized actions on behalf of users, steal session cookies, or even escalate their privileges within the platform. The vulnerability creates a persistent threat vector where any user who accesses a compromised challenge page could be subjected to malicious code execution. This type of vulnerability is particularly dangerous in educational platforms where users might be encouraged to interact with potentially untrusted content, and the sandbox escape allows for execution of dangerous actions that would normally be restricted.
The fix implemented in commit e33da14449a5abcff507e554f66e2141d6683b0a addresses this issue by properly implementing sandboxing mechanisms around the `/workspace/*` routes. This solution aligns with security principle of least privilege and input validation, ensuring that challenge content cannot escape the intended execution boundaries. The mitigation approach follows established security patterns for preventing cross-site scripting and sandbox escape vulnerabilities, similar to those recommended in the CWE database under category CWE-79 for Cross-site Scripting and CWE-276 for Incorrect Default Permissions. From an ATT&CK framework perspective, this vulnerability maps to techniques involving sandbox evasion and privilege escalation, specifically T1059.007 for Command and Scripting Interpreter and T1548.001 for Abuse of System Permissions, demonstrating how a seemingly limited vulnerability can enable broader attack vectors within the platform. The remediation ensures that all content submitted through the workspace routes is properly sanitized and executed in isolated environments that cannot affect the main application's security boundaries.