Ultimate Addons For Beaver BuilderWordPress extension · Brainstormforce
CVE-2023-51401
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 Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Brainstorm Force Ultimate Addons for Beaver Builder allows Relative Path Traversal.This issue affects Ultimate Addons for Beaver Builder: from n/a through 1.35.13.
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 confidenceA relative path traversal vulnerability in Brainstorm Force Ultimate Addons for Beaver Builder allows attackers to access files outside the intended restricted directory through specially crafted file path inputs. This improper limitation of pathname to a restricted directory enables unauthorized file read access.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Ultimate Addons For Beaver BuilderWordPress extension
< 1.35.14CVSS 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
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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.
-
Check installed plugin versionLocate the Ultimate Addons for Beaver Builder plugin in your WordPress plugins directory and identify its installed version number. This is typically found in the plugin header comment in the main PHP file or in a version constant defined by the plugin.Affected if The installed version is lower than 1.35.14 (for example, 1.35.13, 1.35.10, etc.)
-
Identify file handling functionalitySearch the plugin files for functions that handle file paths, file reads, or file inclusion. Look for code that processes user-supplied paths or filenames, particularly functions that accept file path parameters.Affected if The plugin contains file handling code that processes input without proper path sanitization
-
Verify if file read features are accessibleCheck if any publicly accessible endpoints or AJAX actions within the plugin allow file path arguments. Look for parameters that accept file names or paths that could be manipulated for directory traversal.Affected if File read functionality accepts user-controlled path parameters without validation preventing "../" sequences
-
Inspect path validation logicExamine any file access functions in the plugin to determine if they validate that resolved file paths remain within an intended directory. Look for absence of realpath() checks or similar boundary enforcement.Affected if File access functions lack proper path validation that restricts reads to an allowed directory root
You are affected if the installed version of Ultimate Addons for Beaver Builder is below 1.35.14 AND the plugin has accessible file handling functionality that processes user-supplied paths without directory traversal validation.
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.
dbcve · scoped1.35.14
Upgrade Ultimate Addons for Beaver Builder to version 1.35.14 or later. If immediate upgrade is not possible, implement input validation to restrict file paths and prevent directory traversal sequences.
1.35.14
- Update Ultimate Addons for Beaver Builder to version 1.35.14 or later to resolve the path traversal vulnerability
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Ultimate Addons For Beaver Builder
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-51401 — 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-2023-51401 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