CVE-2026-28089
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 Daiquiri daiquiri allows PHP Local File Inclusion.This issue affects Daiquiri: from n/a through <= 1.2.4.
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 confidenceLocal File Inclusion (LFI) vulnerability in ThemeREX Daiquiri <= 1.2.4 allows attackers to include arbitrary files from the server filesystem via improperly controlled filename parameters in PHP include/require statements. This can lead to sensitive file disclosure (e.g., configuration files, credentials) and potentially 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 Daiquiri is installedCheck your WordPress or PHP application for the ThemeREX Daiquiri theme or plugin by examining the theme/plugin directory or checking the installed components list.Affected if ThemeREX Daiquiri is present in your environment
-
Determine the installed versionLocate the version information for ThemeREX Daiquiri (typically in a version.php, style.css header, or plugin readme file within the theme/plugin directory) and compare it to the affected range of 1.2.4 and below.Affected if The installed version is 1.2.4 or any earlier version
-
Locate the vulnerable file inclusion codeSearch the ThemeREX Daiquiri source files for PHP include, include_once, require, or require_once statements that use filename parameters derived from user input (such as $_GET, $_POST, or similar superglobals).Affected if User-controllable parameters are used in include/require statements without proper sanitization
-
Verify the vulnerable parameter is accessibleCheck if the affected PHP scripts containing the insecure file inclusion are directly accessible via HTTP requests (not restricted by authentication, referrer checks, or other access controls).Affected if The vulnerable scripts can be accessed without sufficient access restrictions
-
Check for signs of exploitationReview web server access logs for unusual patterns such as directory traversal sequences (e.g., ../../) in query parameters targeting the affected scripts, or examine application logs for repeated file inclusion attempts.Affected if Log evidence shows directory traversal attempts or unauthorized file access via the vulnerable parameter
Your environment is affected if ThemeREX Daiquiri version 1.2.4 or lower is installed and the vulnerable file inclusion parameter is accessible without proper validation.
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 dataImplement strict input validation and whitelist-based allowlisting for file inclusion paths; disable allow_url_include in PHP configuration; ensure all user-supplied filename parameters are validated against an allowed file list and cannot traverse outside intended directories.
- Consultation3.0 h
- Implementation6.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28089 — 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-28089 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