# Broken property authorization: private response fields

An otherwise permitted object response includes fields the actor is not entitled to read.

**Candidate CWE:** [CWE-862](https://cwe.mitre.org/data/definitions/862.html) · [CWE-863](https://cwe.mitre.org/data/definitions/863.html)

## Test hypothesis

Use a controlled object visible to both actors but containing one owner-only synthetic field. Compare owner and viewer responses, including nested API or GraphQL fields and export serializers.

## Evidence required

The viewer receives the private marker from a protected property despite a documented field-level rule. Save the smallest response fragment proving disclosure. Classify an omitted field-level decision as CWE-862, or an implemented but incorrect decision as CWE-863. Confidentiality loss is the impact, not a reason to add CWE-200.

## Rule out false positives

The UI hiding a field, normal public profile metadata, and intentionally shared properties do not establish a read-side permission boundary.

## Playbook and command references

- [Object, function, and property authorization](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/modules/authz-matrix.html) — Turn identities, tenants, objects, roles, and lifecycle transitions into a reproducible permission matrix.
- [REST, GraphQL, gRPC, WebSocket, and SSE permission parity](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/modules/api-protocols.html) — Carry the same permission invariant across protocols, nested fields, streams, and alternate API versions.

[Find the associated command snippets](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/commands.html?q=Object%2C%20function%2C%20and%20property%20authorization)

## Referenced by these target playbooks

[Web & API](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/web-api.html) · [OSS & self-hosted](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/oss.html) · [Mobile](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/mobile.html) · [Desktop & extensions](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/desktop.html) · [AI, agents & MCP](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/ai.html)

## Report checklist

- [ ] Capture the affected version, configuration, identities, and object ownership.
- [ ] Preserve a valid baseline and a negative control.
- [ ] Reproduce the forbidden data access, action, or state change on controlled fixtures.
- [ ] Explain the intended security rule and why the observed behavior violates it.
- [ ] State prerequisites, uncertainty, cleanup, and the smallest demonstrated impact.

## Conditional ATT&CK mapping

No direct ATT&CK mapping selected. Record the weakness and demonstrated impact without forcing an adversary-behavior classification. See the [mapping guide](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/attack.html).

## Primary references

- [PortSwigger access control](https://portswigger.net/web-security/access-control)
- [MITRE CWE-862](https://cwe.mitre.org/data/definitions/862.html)
- [MITRE CWE-863](https://cwe.mitre.org/data/definitions/863.html)
- [MITRE CWE-200](https://cwe.mitre.org/data/definitions/200.html)

[Back to the complete vulnerability catalog](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/vulnerabilities.html)