01Description
API responses returned more data than the client needed, relying on the front end to hide fields, such as other users' personal details, internal identifiers or password hashes.
02Impact
Anyone calling the API directly sees every field returned, exposing sensitive information that the user interface never displays.
03Severity
Typically
Medium
Typically Medium. Severity follows the data exposed: High for personal, financial or authentication data such as password hashes or tokens.
04How to verify
- 1Compare API responses with what the user interface displays.
- 2Look for personal data, internal flags, hashes and tokens in responses.
- 3Check list endpoints for data about other users.
Testing note: only test systems you are authorized to test, within the agreed scope and rules of engagement. Verification steps are written for professional testers and avoid destructive techniques.
05Remediation
- 1Return only the fields each client needs, using response models per endpoint.
- 2Never rely on the client to filter sensitive data.
- 3Review responses as part of API code review and testing.
Draft findings like this from your own evidence
Book a demo