CVE-2026-27065
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 ThimPress BuilderPress builderpress allows PHP Local File Inclusion.This issue affects BuilderPress: from n/a through <= 2.0.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 · high confidenceThis is a PHP Local File Inclusion (LFI) vulnerability in the BuilderPress plugin by ThimPress. The vulnerability stems from improper control of filenames in include/require statements, allowing attackers to include arbitrary local files. This can lead to exposure of sensitive configuration files, source code, or in some scenarios, remote code execution.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 BuilderPress plugin is installedList installed WordPress plugins via admin dashboard or run: wp plugin list --name=builderpressAffected if The BuilderPress plugin by ThimPress is present in the WordPress installation
-
Determine installed BuilderPress versionCheck the plugin version in the plugin header file (usually builderpress/includes/index.php or via WordPress admin > Plugins > BuilderPress), or query it programmaticallyAffected if The installed version is older than the patched version or falls within an unpatched version range
-
Identify file inclusion functions in plugin codeSearch the builderpress plugin directory for dynamic file inclusion patterns like include($..., require($..., include_once($..., or require_once($... where user input could control the pathAffected if Unsandboxed file inclusion functions that accept variable input are found in the plugin code
-
Inspect web server access logs for LFI patternsReview Apache, Nginx, or other web server access logs for requests to BuilderPress endpoints containing path traversal sequences such as ../, ..\, or direct file paths like /etc/passwdAffected if Suspicious requests with path traversal patterns targeting BuilderPress are present in the logs
The environment is affected if BuilderPress plugin is installed AND uses a version lacking the CVE patch AND the vulnerable file inclusion functionality is accessible to attackers.
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 BuilderPress to the latest patched version. If no patch is available, disable the plugin until a fix is released. Implement strict input validation on any user-controlled parameters used in file inclusion paths.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27065 — 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-27065 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