LiveActive security incident?Get immediate response
CVE Record

CVE-2021-38344: Brizy <= 2.3.11 Authenticated Stored Cross-Site Scripting

The Brizy Page Builder plugin <= 2.3.11 for WordPress was vulnerable to stored XSS by lower-privileged users such as a subscribers. It was possible to add malicious JavaScript to a page by modifying the request sent to update the page via the brizy_update_item AJAX action and adding JavaScript to the data parameter, which would be executed in the session of any visitor viewing or previewing the post or page.

MediumCVSS 6.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Older Brizy Page Builder versions for WordPress allowed a logged-in low-privileged user to store JavaScript in page content. That script could run for visitors or administrators viewing or previewing the affected page, creating risk of data theft, session abuse, and site-content manipulation.

Executive priority

Treat this as a moderate-priority web risk. Patch or validate affected WordPress sites promptly, with higher urgency for customer-facing sites, public registration, or shared contributor environments.

Technical view

CVE-2021-38344 is a stored XSS issue in Brizy Page Builder <= 2.3.11. The source describes abuse of the brizy_update_item AJAX update path, where attacker-controlled JavaScript could be placed in the data parameter and later execute when the page or post was viewed or previewed.

Likely exposure

Exposure is most likely on WordPress sites using Brizy Page Builder version 2.3.11 or earlier, especially where subscribers or other low-privileged accounts exist or user registration is enabled.

Exploitation context

The CVE requires authenticated low-privileged access and no user interaction by the attacker after storage. The bundle does not cite CISA KEV listing or active exploitation evidence, so active exploitation should not be assumed.

Researcher notes

Evidence supports stored XSS with low-privileged authentication in Brizy <= 2.3.11. The bundle does not provide a specific fixed version, exploit-in-the-wild confirmation, or official mitigation beyond the vulnerable version boundary.

Mitigation direction

  • Identify all WordPress sites running Brizy Page Builder.
  • Check Brizy vendor guidance for the fixed release and update accordingly.
  • Prioritize sites with public registration or many low-privileged users.
  • Remove or disable unnecessary subscriber-level accounts.
  • Review affected pages before restoring normal publishing workflows.

Validation and detection

  • Verify Brizy Page Builder is not version 2.3.11 or earlier.
  • Inventory WordPress accounts with subscriber or similar low privileges.
  • Review recent Brizy page updates for unexpected script content.
  • Confirm patched sites reject stored script insertion in staging.
  • Check visitor-facing and preview pages for unexpected JavaScript execution.
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
cve · low confidence lookup

CVE-2021-38344 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
Medium
CVSS
6.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:N

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
6.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N3.12.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.4Medium
CVSS 3.1 vector shape for CVE-2021-38344Attack 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:N

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.

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.