LiveActive security incident?Get immediate response
CVE Record

CVE-2026-27986: WordPress OsTende theme <= 1.4.3 - Local File Inclusion vulnerability

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in ThemeREX OsTende ostende allows PHP Local File Inclusion.This issue affects OsTende: from n/a through <= 1.4.3.

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-27986 affects the WordPress OsTende theme by ThemeREX through version 1.4.3. A remote unauthenticated attacker may be able to make the site include unintended local PHP files. The CVSS score is 8.1, rated high. There is no provided evidence of active exploitation or CISA KEV listing.

Executive priority

Prioritize identification and remediation for internet-facing WordPress sites using OsTende. The issue has high potential impact, but current sources do not show known exploitation. Act promptly, especially where the theme supports public-facing business services.

Technical view

The issue is described as improper filename control in a PHP include/require statement, categorized as CWE-98. The CVE states it allows PHP Local File Inclusion in OsTende through 1.4.3. The vector is network reachable, no privileges, no user interaction, high complexity, with high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is limited to WordPress sites using the ThemeREX OsTende theme at version 1.4.3 or earlier. The source bundle does not identify other affected products or confirm whether inactive installed copies are exploitable.

Exploitation context

No active exploitation is supported by the provided sources, and the CVE is not marked KEV. The vulnerability is remotely reachable without authentication, but rated high attack complexity, suggesting exploitation may require specific conditions not detailed in the sources.

Researcher notes

Evidence is limited to the CVE record and Patchstack database reference. The bundle does not provide exploit details, fixed version, affected code paths, or vendor advisory text. Avoid assuming exploitation in the wild or specific remediation beyond checking official guidance.

Mitigation direction

  • Inventory WordPress sites for the OsTende theme and installed version.
  • Treat OsTende versions 1.4.3 and earlier as affected.
  • Check ThemeREX and Patchstack guidance for an update or vendor mitigation.
  • Remove the theme if it is unnecessary and business-approved.
  • Apply compensating monitoring until vendor remediation is confirmed.

Validation and detection

  • Confirm whether OsTende is installed on each WordPress site.
  • Record the exact theme version and compare with 1.4.3 or earlier.
  • Review vendor or Patchstack advisories for fixed-version information.
  • Check logs for unusual requests to theme PHP endpoints.
  • Verify remediation status after any update, removal, or vendor-recommended change.
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-27986 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-27986Attack 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
ThemeREXOsTendeostende, 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.