dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-69055

MEDIUM · 6.5 CVSS v3.1 Published 2026-01-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in SeaTheme BM Content Builder bm-builder allows Path Traversal.This issue affects BM Content Builder: from n/a through < 3.16.3.3.

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 confidence

Path traversal vulnerability in SeaTheme's BM Content Builder plugin allows attackers to escape the intended restricted directory and access arbitrary files on the server through manipulation of file path inputs using '../' sequences. The flaw exists in the bm-builder component and affects versions prior to 3.16.3.3.

MitigationUpdate BM Content Builder to version 3.16.3.3 or later to obtain the vendor patch. If patching is delayed, restrict file access permissions and audit the plugin's file handling functions for proper path validation.

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if BM Content Builder plugin is installed
    Check your WordPress plugins directory or admin panel for the BM Content Builder plugin by SeaTheme. Look for folder names containing 'bm-content-builder', 'bm-builder', or 'bm-content' in wp-content/plugins/
    Affected if The plugin is present in the WordPress installation
  2. Determine the installed plugin version
    Open the main plugin file (usually index.php or the main PHP file in the plugin folder) and look for a version comment or constant, or check the plugin header in the main PHP file for 'Version: x.x.x'
    Affected if The version is lower than 3.16.3.3 or the version cannot be determined (unlisted)
  3. Verify the bm-builder component is active
    Check the WordPress admin under the BM Content Builder menu or inspect the database wp_options table for active bm-builder related options and shortcodes registered by the plugin
    Affected if The bm-builder component is enabled and accessible on the site
  4. Inspect file handling functions for path traversal exposure
    Examine the plugin's PHP files in the bm-builder folder, specifically looking for file inclusion, file read/write, or file upload functions that accept user input without proper sanitization of '../' sequences. Search for functions like include, require, file_get_contents, readfile, or similar that use variables derived from request parameters
    Affected if File handling functions exist that accept unsanitized path input from users
  5. Check web server access logs for suspicious path traversal patterns
    Review web server access logs (Apache/Nginx) for requests to bm-builder endpoints containing '../' sequences, such as '?file=../../wp-config.php' or similar patterns

You are affected if BM Content Builder plugin is installed with a version prior to 3.16.3.3 and the bm-builder component is active, allowing potential path traversal via unsanitized file path inputs.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update BM Content Builder to version 3.16.3.3 or later to obtain the vendor patch. If patching is delayed, restrict file access permissions and audit the plugin's file handling functions for proper path validation.

Recommended fix Moderate confidence

BM Content Builder version 3.16.3.3

  1. 1. Backup your WordPress site and database before making any changes.
  2. 2. Navigate to your WordPress admin dashboard.
  3. 3. Go to Plugins > Installed Plugins.
  4. 4. Find 'BM Content Builder' (by SeaTheme) in the plugin list.
  5. 5. Check if an update is available. If not, you may need to manually download version 3.16.3.3 from the vendor.
  6. 6. Update the plugin to version 3.16.3.3 or later.
  7. 7. Verify the update was successful by checking the plugin version in your plugins list.
  8. 8. Test the BM Content Builder functionality to ensure it still works as expected.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-69055 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-69055 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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