Security Test: Invalid Persisted Query¶

Description¶

Default Severity: info

This issue happens when a query saved for future use no longer matches the current setup on the server. If a query refers to something that doesn’t exist anymore, an attacker might intentionally trigger errors or unpredictable responses, potentially revealing sensitive details about the system or causing service disruptions. The most common mistake is not updating or cleaning up these saved queries when the underlying system changes, leaving a gap that bad actors might use to destabilize the service or probe for weaknesses.

Configuration¶

Identifier: schema/invalid_persisted_query

Examples¶

All configuration available:

checks:
  schema/invalid_persisted_query:
    skip: false # default

Compliance and Standards¶