An issue exists where unauthenticated attackers can extract sensitive information from non-public post objects, such as wp block synced patterns, which are typically protected by WordPress core. This occurs because a REST route is registered with a `permission callback` of ` return true` and passes the user-supplied `context` parameter directly to the `prepare item for response()` function without performing necessary permission checks via `get item permissions check()` or `check read permission()`. Additionally, the underlying query allows an arbitrary `post type` value without verifying public or `show in rest` visibility flags. This allows the exposure of sensitive edit-context fields, including raw title, raw content body, password, meta, status, and guid.