LiveActive security incident?Get immediate response
CVE Record

CVE-2021-38346: Brizy <= 2.3.11 Authenticated Unrestricted File Upload and Path Traversal

The Brizy Page Builder plugin <= 2.3.11 for WordPress allowed authenticated users to upload executable files to a location of their choice using the brizy_create_block_screenshot AJAX action. The file would be named using the id parameter, which could be prepended with "../" to perform directory traversal, and the file contents were populated via the ibsf parameter, which would be base64-decoded and written to the file. While the plugin added a .jpg extension to all uploaded filenames, a double extension attack was still possible, e.g. a file named shell.php would be saved as shell.php.jpg, and would be executable on a number of common configurations.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A logged-in WordPress user could abuse Brizy Page Builder up to version 2.3.11 to write files into chosen locations. On some server configurations, this could allow attacker-controlled code to run and lead to site takeover.

Executive priority

Treat as high priority for internet-facing WordPress sites using Brizy. The business risk is website takeover from a low-privilege account, but urgency depends on whether the plugin is present and exposed.

Technical view

The brizy_create_block_screenshot AJAX action accepted attacker-controlled filename and file content inputs. The id parameter allowed ../ path traversal, and ibsf content was base64-decoded and written with a .jpg suffix. Double extensions could remain executable on some common configurations.

Likely exposure

Exposure is likely limited to WordPress sites running Brizy Page Builder version 2.3.11 or earlier with attacker-accessible authenticated accounts. Risk increases where web servers execute double-extension files.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. Exploitation requires authenticated access, but CVSS rates privileges required as low and no user interaction as needed.

Researcher notes

The CVE metadata lists CWE-79, but the described behavior is unrestricted file upload plus path traversal. Evidence for a named fixed version is not included in the supplied bundle, so remediation should follow current vendor guidance.

Mitigation direction

  • Identify all WordPress sites using Brizy Page Builder.
  • Update Brizy beyond affected versions using vendor guidance.
  • Restrict or remove unnecessary WordPress user accounts.
  • Review server handling of double-extension uploads.
  • Check webroot and upload paths for unexpected files.

Validation and detection

  • Confirm installed Brizy Page Builder version on each WordPress site.
  • Review WordPress users with low-privilege authenticated access.
  • Inspect logs for brizy_create_block_screenshot AJAX activity.
  • Look for suspicious .php.jpg files in writable web paths.
  • Verify web server does not execute uploaded double-extension files.
Prepared
Confidence
high
Sources
3

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 · medium confidence lookup

CWE-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell 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-2021-38346 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
8.8 (3.1)
Known Exploited
No
Published

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

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
2Source 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
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2021-38346Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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
Brizy.ioBrizy - Page Builder2.3.11Listed
Weakness

CWE details

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