> For clean Markdown of this page, append .md to its URL. For the complete documentation index, see https://www.superagent.sh/llms.txt.


Review whether backend code stops honoring permissions after they are revoked.

# Revoked permissions in backend code


[← Back to attack scenarios](https://www.superagent.sh/docs/products/red-teaming/attack-scenarios)

Permissions can be checked in several places, including when a session starts or when a request arrives. This scenario checks whether the paths that authorize work still honor an old permission after access changes.

It applies to code that manages sessions, credentials, or membership. A finding points to the part of the system where authorization stayed valid after revocation.

The app lists this scenario as **Use stale authorization after access is revoked** (`REPO-05`) in [Repository Red Teaming](https://www.superagent.sh/docs/products/red-teaming/repositories).

## Standards and guidance

[OWASP A01:2025 Broken Access Control](https://top10.owasp.org/2025/A01_2025-Broken_Access_Control/)

---
Source: https://www.superagent.sh/docs/products/red-teaming/attack-scenarios/repository-revoked-permissions
Index: https://www.superagent.sh/llms.txt
