CVE-2026-57791
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 ThemeMove Brook brook allows PHP Local File Inclusion.This issue affects Brook: from n/a through <= 2.9.0.
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 confidenceThe ThemeMove Brook WordPress theme (versions <= 2.9.0) contains a PHP Local File Inclusion (LFI) vulnerability where the application improperly controls the filename parameter in include/require statements. This allows an attacker to potentially read sensitive server files or achieve remote code execution in certain configurations.
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.
-
Identify if Brook theme is installedNavigate to WordPress admin dashboard, go to Appearance > Themes, and confirm the Brook theme by ThemeMove is active or installed.Affected if The Brook theme by ThemeMove is present in the WordPress installation.
-
Check the installed theme versionAccess the theme's style.css file in wp-content/themes/brook/ and locate the 'Version' header in the file comments, or view theme details in WordPress admin under Appearance > Themes.Affected if The version number is 2.9.0 or lower.
-
Locate file inclusion code in theme filesSearch theme PHP files for include, require, include_once, or require_once statements that use a variable or request parameter for the file path (e.g., include($_GET['filename'])). Common locations include files in the 'inc/' or 'include/' directories.Affected if File inclusion code uses an unsanitized parameter (commonly 'filename', 'page', 'template', or similar) from user input.
-
Test if vulnerable parameter is accessible via web requestSend a crafted HTTP request to the affected page with a directory traversal pattern in the suspected parameter (e.g., ?filename=../../../../wp-config.php). Observe if the server returns file contents or an error revealing the file inclusion behavior.Affected if The parameter accepts directory traversal sequences and the server responds with file contents or reveals file path information.
A user is affected if the Brook theme version is 2.9.0 or lower AND the theme contains file inclusion code using unsanitized request parameters that are accessible via web requests.
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 to a patched version of the Brook theme that properly sanitizes and validates all file inclusion parameters. Until a patch is available, implement web application firewall rules to block directory traversal patterns in request parameters.
- 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-57791 — 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-57791 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