Cross-owner template type modification via mismatched identifier
Published Aug 4, 2026 · Updated Aug 4, 2026
Authorization bypass in the Brizy WordPress plugin before 2.8.19 allows remote authenticated users to alter other users' template types. The brizy_set_template_type AJAX handler authorizes a different post parameter from the template_id used to update brizy_template_type metadata. Contributor access, a valid Brizy nonce, and another user's template ID are required; the effect is limited to changing that template's type assignment.
Summary
What happened
Authorization bypass in the Brizy WordPress plugin before 2.8.19 allows remote authenticated users to alter other users' template types. The brizy_set_template_type AJAX handler authorizes a different post parameter from the template_id used to update brizy_template_type metadata. Contributor access, a valid Brizy nonce, and another user's template ID are required; the effect is limited to changing that template's type assignment.
The record
- CVE
- CVE-2026-16070
- Published
- Aug 4, 2026
- Updated
- Aug 4, 2026
- Vendor
- ThemeFuse
- Product
- Brizy - Page Builder
- Classifications
- CWE-639, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 4, 2026CVE publishedPublication date reported by the CVE source.
- Aug 4, 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.19
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 authenticated AJAX proof of conceptfunctional · 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