CVE-2025-69319
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedImproper 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceCode injection vulnerability in Beaver Builder plugin versions up to 2.9.4.1 allows unauthenticated attackers to inject and execute malicious code due to improper control of code generation, likely through unsanitized user input being used in dynamic PHP code execution functions.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Beaver Builder plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Beaver Builder' (also known as 'Page Builder by Beaver Builder' or 'Beaver Builder Plugin'). Check if it is activated.Affected if The plugin is installed and activated
-
Check the installed Beaver Builder versionIn WordPress admin, go to Plugins > Installed Plugins, find Beaver Builder, and note the version number displayed. Alternatively, check the version in the plugin's main PHP file (typically at /wp-content/plugins/bb-plugin/ or /wp-content/plugins/beaver-builder-lite-version/)Affected if Version is 2.9.4.1 or lower (any version up to and including 2.9.4.1)
-
Confirm the plugin handles user input publiclyVerify that the Beaver Builder plugin is configured to allow frontend editing, custom modules, or template loading that processes user-supplied data. Check plugin settings under Beaver Builder > Settings to see if 'Frontend Editor' or similar public-facing features are enabled.Affected if Frontend editing or public template/module features are enabled and accessible to unauthenticated users
-
Identify vulnerable dynamic code execution patternsExamine Beaver Builder plugin files for usage of dangerous PHP functions that execute dynamic code, specifically: eval(), preg_replace() with /e modifier, extract(), create_function(), or similar. Search in the /bb-plugin/ directory, particularly in files handling user input or dynamic content rendering.Affected if These functions are present and process unsanitized user input from request parameters or database content
If Beaver Builder plugin version 2.9.4.1 or lower is installed with public-facing features enabled, the environment is affected by this code injection vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to the latest Beaver Builder version immediately. If upgrade is not possible, restrict access to affected endpoints and audit the codebase for dangerous functions like eval(), preg_replace() with /e modifier, or extract()/create_function() that handle user input.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-69319 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-69319 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data