LiveActive security incident?Get immediate response
CVE Record

CVE-2020-36714: Brizy < 1.0.126 - Authorization Bypass to Settings Updates

The Brizy plugin for WordPress is vulnerable to authorization bypass due to a incorrect capability check on the is_administrator() function in versions up to, and including, 1.0.125. This makes it possible for authenticated attackers to access and interact with available AJAX functions.

HighCVSS 7.4Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This flaw let logged-in WordPress users bypass intended permission checks in the Brizy Page Builder plugin and reach AJAX functions meant for higher-privileged users. For an affected site, that can mean unauthorized settings changes or other limited impact to confidentiality, integrity, and availability depending on exposed functions.

Executive priority

Treat as a high-priority WordPress plugin update where Brizy is installed, especially on sites allowing public registration or many low-privileged users. No active exploitation is cited, but the low complexity and authenticated access requirement make remediation time-sensitive.

Technical view

CVE-2020-36714 is a CWE-285 authorization bypass in Brizy Page Builder up to and including 1.0.125. The issue stems from an incorrect capability check in is_administrator(), allowing authenticated low-privileged attackers to access and interact with available AJAX functions. CVSS 3.1 is 7.4 high.

Likely exposure

Exposure is limited to WordPress sites running Brizy Page Builder versions before 1.0.126. Sites with many authenticated users, such as customer, subscriber, contributor, or membership accounts, have higher practical exposure.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. Exploitation requires an authenticated account and depends on which Brizy AJAX functions are reachable on the affected site.

Researcher notes

Primary evidence identifies an incorrect capability check in is_administrator() and authenticated access to AJAX functions. The bundle’s affected metadata is sparse and inconsistent with the narrative, so version validation should rely on the CVE description and referenced advisories.

Mitigation direction

  • Update Brizy Page Builder to version 1.0.126 or later.
  • If immediate update is impossible, disable the plugin until vendor guidance is applied.
  • Remove unnecessary WordPress user accounts and reduce low-privileged account exposure.
  • Review vendor and Wordfence guidance for any additional remediation details.

Validation and detection

  • Inventory WordPress sites for Brizy Page Builder installations.
  • Confirm installed Brizy versions are later than 1.0.125.
  • Review WordPress users for unnecessary authenticated access.
  • Check logs for unusual authenticated admin-ajax.php activity involving Brizy functions.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-285: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Privilege behavior lookup

The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-36714 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.4CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L3.13.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.4High
CVSS 3.1 vector shape for CVE-2020-36714Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
themefusecomBrizy – Page Builder0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-285 · source CWE mapping

Improper Authorization

Improper Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.