What problem does it solve?
GraphQL APIs often expose incomplete schemas publicly, restrict introspection, or accept undocumented parameters that can reveal authorization gaps and hidden functionality.
Core Features & Use Cases
- Schema-first discovery: Start with introspection probes to map available types, fields, and capabilities even when the endpoint partially supports discovery.
- Hidden parameter and schema abuse: Identify undocumented fields, permissive input shapes, and “extra” request body attributes by leveraging type probes and error-based inference.
- Authorization gap exploration: Test for IDOR-style issues, nested object authorization weaknesses, and role-dependent field exposure.
- Use case: When a target shows only a minimal “user profile” view, use this playbook to enumerate schema-referenced fields, attempt hidden parameter variations, and surface fields that appear in the schema but are not properly protected.
Quick Start
Use graphql-and-hidden-parameters to probe schema introspection and hunt for hidden fields and authorization gaps in a GraphQL endpoint.