Clarify Summary wording for WSTG-ATHZ-02 Authorization Schema test#1289
Merged
kingthorin merged 2 commits intoOWASP:masterfrom Jan 29, 2026
Merged
Conversation
|
The following issues were identified: |
kingthorin
approved these changes
Jan 29, 2026
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
2 participants
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.
Related Issue
Fixes #1089
Description
This PR clarifies the Summary section of the Testing for Bypassing Authorization Schema
test case (WSTG-ATHZ-02).
The update removes ambiguity between authentication-related scenarios (unauthenticated
or post-logout access) and authorization-focused testing, and clearly emphasizes that
the primary intent of this test case is to identify authorization weaknesses such as
horizontal and vertical privilege escalation for authenticated users.
Detailed unauthenticated and post-authentication scenarios remain unchanged and are
covered in the How to Test section.
Scope Note
This PR is intentionally limited to wording changes in the Summary section only.
No test logic, procedures, examples, or other sections were modified.
AI Tool Disclosure