Security readout for executives and security teams
Plain-English summary
CVE-2022-36425 affects the Beaver Builder WordPress page builder plugin through version 2.5.4.3. It is a broken access control issue that could let a logged-in user perform unauthorized actions with limited impact to integrity and availability. Treat it as moderate business risk for WordPress sites using this plugin.
Executive priority
Handle through normal vulnerability management, with faster action for public WordPress sites or sites with many contributor accounts. It is not flagged as known exploited, but outdated page-builder plugins can affect visible site content and availability.
Technical view
The CVE describes broken access control in Beaver Builder – WordPress Page Builder <= 2.5.4.3. CVSS 3.1 is 5.4 with network attack vector, low complexity, low privileges required, no user interaction, and low integrity and availability impact. The provided sources do not include technical root cause detail or a named fixed version.
Likely exposure
Exposure is limited to WordPress installations running Beaver Builder plugin version 2.5.4.3 or earlier. The CVSS privileges requirement indicates exploitation requires an authenticated low-privileged account, reducing broad unauthenticated internet risk.
Exploitation context
CISA KEV status is false, and the provided sources do not state active exploitation. Public details in the bundle are limited, so do not assume exploit availability, exploitation in the wild, or specific attack paths without vendor or threat-intelligence confirmation.
Researcher notes
The source bundle provides affected version, CVSS vector, CWE-264, and references, but not endpoint details, exploit mechanics, or a fixed version. Validation should focus on version exposure, authentication boundaries, role permissions, and vendor-confirmed remediation status.
Mitigation direction
- Inventory WordPress sites for the Beaver Builder plugin and exact installed versions.
- Prioritize remediation where version 2.5.4.3 or earlier is installed.
- Check Patchstack, WordPress.org, and vendor guidance for the fixed release before updating.
- Limit WordPress accounts with plugin or content-editing privileges.
- Remove or disable the plugin where it is not operationally required.
- Back up and test sites before plugin changes in production.
Validation and detection
- Confirm plugin version from WordPress admin or approved asset inventory records.
- Identify any sites running Beaver Builder version 2.5.4.3 or earlier.
- Review WordPress user roles for unnecessary low-privileged accounts with editing access.
- Check recent content, layout, and plugin configuration changes for unauthorized activity.
- After remediation, verify the installed version is outside the affected range.
- Document evidence of vendor guidance used for the remediation decision.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-264: 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 lookupCVE-2022-36425 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L2.82.5Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.4MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
Source materials
- CVE List V5 sourceCVE List V5
- https://patchstack.com/database/vulnerability/beaver-builder-lite-version/wordpress-beaver-builder-plugin-2-5-4-3-broken-access-control-vulnerability/_s_id=cveCVE reference · x_refsource_CONFIRM
- https://wordpress.org/plugins/beaver-builder-lite-version/#developersCVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Permissions, Privileges, and Access Controls
Permissions, Privileges, and Access Controls represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.