LiveActive security incident?Get immediate response
CVE Record

CVE-2026-28089: WordPress Daiquiri theme <= 1.2.4 - Local File Inclusion vulnerability

Improper 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.

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-28089 is a high-severity local file inclusion issue in the WordPress Daiquiri theme from ThemeREX, affecting versions through 1.2.4. A remote, unauthenticated attacker may be able to cause the site to include unintended local files. The public sources do not confirm active exploitation or name a fixed version.

Executive priority

Treat as a priority for WordPress asset owners using Daiquiri. The potential impact is high, but urgency depends on whether the theme is deployed and whether vendor remediation is available. Start with inventory and removal or update decisions.

Technical view

The flaw is classified as CWE-98: improper control of filenames used in PHP include/require statements. CVSS 3.1 is 8.1 with network access, no privileges, no user interaction, high attack complexity, and high confidentiality, integrity, and availability impact. The CVE description identifies Daiquiri <= 1.2.4 as affected.

Likely exposure

Exposure is limited to WordPress sites using the ThemeREX Daiquiri theme at version 1.2.4 or earlier. Sites not using this theme are not indicated as affected by the provided sources.

Exploitation context

No provided source states active exploitation, and the CVE is not marked as CISA KEV in the bundle. The CVSS vector indicates exploitation is remotely reachable without authentication, but attack complexity is high.

Researcher notes

Source detail is limited. The CVE references PHP file inclusion behavior and Patchstack’s vulnerability entry, but the bundle does not provide vulnerable parameters, exploit evidence, or a fixed version. Avoid assuming broader ThemeREX product impact.

Mitigation direction

  • Inventory WordPress sites for the ThemeREX Daiquiri theme and version.
  • Check ThemeREX, WordPress theme marketplace, or Patchstack for vendor remediation guidance.
  • Update the theme if a fixed version is available from trusted sources.
  • Disable or remove the theme where it is unused or cannot be remediated.
  • Apply compensating monitoring until vendor guidance or a fixed version is confirmed.

Validation and detection

  • Confirm whether Daiquiri is installed on each WordPress site.
  • Record the installed Daiquiri version and compare against <= 1.2.4.
  • Review vendor and Patchstack advisories for fixed-version information.
  • Check web logs for unusual requests to theme PHP endpoints or include-like parameters.
  • Validate remediation by confirming the vulnerable theme version is no longer present.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-98: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-28089 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.1CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H2.25.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.1High
CVSS 3.1 vector shape for CVE-2026-28089Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
ThemeREXDaiquiridaiquiri, 0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-98 · source CWE mapping

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.