CVE-2026-32400
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 Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in ThemetechMount Boldman boldman allows PHP Local File Inclusion.This issue affects Boldman: from n/a through <= 7.7.
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 confidenceThe ThemetechMount Boldman theme <= 7.7 contains a PHP Local File Inclusion (LFI) vulnerability where user-supplied input is improperly used in include/require statements, allowing attackers to read arbitrary files on the server filesystem via directory traversal sequences.
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.
-
Confirm Boldman theme installationCheck your WordPress installation for the Boldman theme in wp-content/themes/ directory (look for folder named 'boldman' or similar)Affected if The Boldman theme folder exists in the themes directory
-
Identify installed theme versionOpen the theme's style.css file in the boldman theme folder and look for the 'Version:' declaration in the file header commentsAffected if The version number is 7.7 or lower
-
Locate PHP files using dynamic includesSearch the theme's PHP files for patterns like 'include(', 'require(', 'include_once(', 'require_once(' combined with variables such as $_GET, $_POST, $_REQUEST, or $_SERVER parametersAffected if Theme PHP files contain include/require statements using user-supplied input without proper sanitization
-
Identify the vulnerable parameterExamine identified PHP files for parameters that accept file paths (common names include 'page', 'file', 'template', 'path', 'slug') and are used in include/require operationsAffected if A parameter accepts directory traversal sequences (../) and passes user input directly to include/require functions
-
Test for directory traversal exposureUsing a safe read-only method, review the code flow to confirm the parameter can reach the filesystem without validation - do not actually exploit, just trace the data flow from the request to the include statementAffected if User-controllable input reaches an include/require statement without sanitizing ../ sequences
You are affected if the Boldman theme version is 7.7 or lower AND your server exposes a WordPress endpoint using the vulnerable code path that accepts file path parameters.
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 dataUpdate the Boldman theme to the latest patched version; if no patch exists, disable or remove the theme and implement WAF rules to block directory traversal patterns (e.g., ../) in request parameters.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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 $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32400 — 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-2026-32400 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