Repository navigation
Security: Validate REST course access - refs GHSA-h4w8-c66c-p8r2 - #9238
Merged
christianbeeznest merged 1 commit intoOct 16, 2026
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
REST v2 accepted a client-supplied course context without checking whether the authenticated webservice user could access that course.
The REST course context is now validated before it is stored in the session. Access follows the existing course visibility, membership, session and contextual role rules, while platform administrators keep their existing access.
Verified against a running 1.11.x instance:
Refs GHSA-h4w8-c66c-p8r2