Authenticated post disclosure via mismatched identifier checks
Published Aug 1, 2026 · Updated Aug 1, 2026
Authorization bypass in ThemeFuse Brizy - Page Builder before 2.8.18 allows remote authenticated users to read arbitrary post content. The brizy_get_post_info handler authorizes a checked post parameter but loads the record identified by the separate, user-controlled post_id value. Contributor access and a valid brizy-api nonce are required; successful requests expose other users' private, pending, and draft posts without modifying them.
Summary
What happened
Authorization bypass in ThemeFuse Brizy - Page Builder before 2.8.18 allows remote authenticated users to read arbitrary post content. The brizy_get_post_info handler authorizes a checked post parameter but loads the record identified by the separate, user-controlled post_id value. Contributor access and a valid brizy-api nonce are required; successful requests expose other users' private, pending, and draft posts without modifying them.
The record
- CVE
- CVE-2026-14195
- Published
- Aug 1, 2026
- Updated
- Aug 1, 2026
- Vendor
- ThemeFuse
- Product
- Brizy - Page Builder
- Classifications
- CWE-639, T1213
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 1, 2026CVE publishedPublication date reported by the CVE source.
- Aug 1, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2.8.18
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- WPScan brizy_get_post_info proof of conceptproof of concept · validated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo