Brizy lets Contributors read private and unpublished posts
Brizy before 2.8.18 returns post content through a request handler without adequately checking whether the caller may read the selected post. A Contributor-or-higher user can supply another post's identifier and retrieve content belonging to other users, including private, pending and draft posts. The published record does not disclose the handler route or action, post-ID parameter, authorization function or response format.
- Component
- Brizy
- Plugin slug
brizy- Affected
- < 2.8.18
- Safe version
2.8.18- Published
- Aug 01, 2026
- Weakness
- Not assigned
This CVE was published Aug 01, 2026 and is one of 31 known issues for this plugin.
Update, patch or deactivate.
Update Brizy to 2.8.18 or later. Review Contributor activity for enumeration of posts outside their ownership, determine which private or unpublished content may have been returned, and rotate secrets or handle personal information found in exposed drafts appropriately.
A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
The Brizy WordPress plugin before 2.8.18 does not properly verify authorization on a request handler before returning post content, allowing users with the Contributor role or higher to read the content of arbitrary posts, including other users' private, pending, and draft posts.