LiveActive security incident?Get immediate response
CVE Record

CVE-2025-69319: WordPress Beaver Builder plugin <= 2.9.4.1 - Arbitrary Code Execution vulnerability

Improper Control of Generation of Code ('Code Injection') vulnerability in Beaver Builder Beaver Builder beaver-builder-lite-version allows Code Injection.This issue affects Beaver Builder: from n/a through <= 2.9.4.1.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2025-69319 affects the WordPress Beaver Builder plugin through version 2.9.4.1. It is a code injection issue that may let a logged-in, low-privileged attacker execute arbitrary code. The CVSS score is 7.5, high. No provided source confirms active exploitation.

Executive priority

Treat as a high-priority WordPress plugin issue for affected sites, especially public sites with user registration or many contributors. Prioritize inventory, version validation, and vendor-guided updating.

Technical view

The CVE describes CWE-94 Improper Control of Generation of Code in beaver-builder-lite-version. The vector is AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H, meaning network access, high attack complexity, low privileges, and no user interaction, with high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is likely limited to WordPress sites running Beaver Builder beaver-builder-lite-version through 2.9.4.1, especially where untrusted or numerous low-privilege accounts exist.

Exploitation context

The sources do not provide exploit details or confirm public exploitation. CISA KEV is false in the provided bundle. The vulnerability requires low privileges and high complexity, reducing likelihood but not impact.

Researcher notes

Evidence is limited to the CVE record and Patchstack database reference. The affected range is through 2.9.4.1, but the provided sources do not name a fixed version, patch date, or exploitation evidence.

Mitigation direction

  • Inventory WordPress sites using Beaver Builder beaver-builder-lite-version.
  • Check whether installed versions are 2.9.4.1 or earlier.
  • Review Beaver Builder and Patchstack guidance for fixed versions or mitigations.
  • Update to a vendor-supported fixed release when confirmed available.
  • Disable or remove the plugin where it is unnecessary.
  • Restrict low-privilege account creation and review existing WordPress users.

Validation and detection

  • Confirm plugin name and version from WordPress administration or asset inventory.
  • Prioritize externally reachable WordPress sites first.
  • Verify whether any vendor advisory identifies a fixed version.
  • Review WordPress user accounts for unexpected low-privilege access.
  • Check application and server logs for unusual plugin-related errors or changes.
Prepared
Confidence
medium
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-94: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. 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

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. 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-2025-69319 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.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/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
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H1.65.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2025-69319Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/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
Beaver BuilderBeaver Builderbeaver-builder-lite-version, 0unaffected
Weakness

CWE details

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

CWE-94 · source CWE mapping

Improper Control of Generation of Code ('Code Injection')

Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.