CVE-2025-59002
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 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 confidenceA path traversal vulnerability in SeaTheme BM Content Builder's bm-builder component allows attackers to access files outside the restricted directory by manipulating file paths with '../' sequences. This improper limitation of pathname to a restricted directory enables unauthorized file system access.
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
- Changed
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/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.
-
Identify BM Content Builder versionLocate the BM Content Builder plugin/theme version number in your WordPress admin panel under Plugins > BM Content Builder, or check the version in the main plugin file header (commonly bm-builder.php or similar)Affected if The installed version is lower than 3.16.3.3
-
Confirm bm-builder component is activeCheck your WordPress plugins or theme components list to verify the bm-builder component is installed and activatedAffected if The bm-builder component is enabled and running
-
Check for existing path traversal protectionInspect the web server or application configuration for any existing input validation rules that filter or reject '../' sequences in file path parametersAffected if No traversal protection or input validation is currently implemented on file path parameters
-
Test for path traversal vulnerabilitySend a benign test request to a bm-builder endpoint using a path like '../../../wp-config.php' to observe if the application allows directory traversal outside the restricted directoryAffected if The application returns file contents or allows access to files outside the intended directory
-
Review recent access logsExamine web server access logs for any requests to bm-builder endpoints containing '../' sequences that may indicate exploitation attemptsAffected if Suspicious traversal patterns are found in access logs
You are affected if BM Content Builder version is below 3.16.3.3 AND the bm-builder component is currently enabled in your environment.
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 BM Content Builder to version 3.16.3.3 or later. Until patched, disable the bm-builder component and implement strict input validation on all file path parameters to reject traversal sequences.
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-59002 — 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-59002 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