CVE-2026-28067
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 ThemeREX Bassein bassein allows PHP Local File Inclusion.This issue affects Bassein: from n/a through <= 1.0.15.
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 PHP Local File Inclusion vulnerability in the ThemeREX Bassein theme allows attackers to manipulate filename parameters in include/require statements. Due to improper input validation, malicious files can be included and executed server-side, potentially leading to 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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.
-
Identify if ThemeREX Bassein theme is installedSearch for theme files bearing the ThemeREX Bassein name in your web root, typically under wp-content/themes/ for WordPress implementationsAffected if ThemeREX Bassein theme files are present in the environment
-
Determine the installed theme versionLocate the theme's style.css or version file and read the declared version numberAffected if The installed version is older than the patched version (compare against the vendor's official release notes)
-
Inspect include/require statements for vulnerable parameter handlingSearch the theme's PHP files for include(), require(), include_once(), or require_once() calls where user-supplied input (e.g., $_GET, $_POST) is used directly in the filename parameter without sanitizationAffected if Such insecure include/require patterns exist in the theme code and user-controllable input reaches them
-
Verify the attack surface is reachableDetermine whether the affected PHP scripts handling the file inclusion are accessible without authentication or can be reached via web requestsAffected if The vulnerable include/require logic is exposed via accessible URL endpoints
-
Check PHP configuration for allow_url_includeReview php.ini or run phpinfo() to check if the allow_url_include directive is enabledAffected if allow_url_include is set to On, which can worsen the impact by allowing remote file inclusion
Your environment is affected if the ThemeREX Bassein theme is installed and the vulnerable file inclusion code with unsanitized user input is present and accessible.
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 to the latest patched version of the ThemeREX Bassein theme. Until an update is available, implement strict input validation using whitelists for file paths and disable allow_url_include in PHP configuration.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28067 — 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-28067 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