LiveActive security incident?Get immediate response
CVE Record

CVE-2026-27337: WordPress Chronicle - Lifestyle Magazine & Blog WordPress Theme theme <= 1.0 - Local File Inclusion vulnerability

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in AncoraThemes Chronicle - Lifestyle Magazine & Blog WordPress Theme chronicle allows PHP Local File Inclusion.This issue affects Chronicle - Lifestyle Magazine & Blog WordPress Theme: from n/a through <= 1.0.

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-27337 affects the AncoraThemes Chronicle WordPress theme version 1.0 and earlier. It is a local file inclusion flaw that could let an unauthenticated remote attacker cause the site to include unintended local files. The CVSS score is high, but exploitation complexity is rated high. No source provided confirms active exploitation.

Executive priority

Treat this as a high-priority WordPress exposure review, especially for public sites using the Chronicle theme. Do not assume compromise from the CVE alone. Confirm usage first, then update, replace, or remove the vulnerable theme based on vendor guidance.

Technical view

The CVE describes CWE-98: improper control of a filename used in a PHP include/require statement. The affected product is Chronicle - Lifestyle Magazine & Blog WordPress Theme through version 1.0. CVSS 3.1 is 8.1 with AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H. Public data does not identify a patched version or detailed prerequisites.

Likely exposure

Exposure is likely limited to WordPress sites that have the Chronicle theme installed at version 1.0 or earlier. The CVE data marks other/default versions as unaffected, but asset owners should verify the exact installed theme name and version.

Exploitation context

The issue is remotely reachable and requires no authentication or user interaction per CVSS. Attack complexity is high, suggesting specific conditions may be needed. The source bundle does not show CISA KEV listing, public exploitation, proof-of-concept code, or in-the-wild attacks.

Researcher notes

Evidence is thin beyond the CVE and Patchstack entry. The record names local file inclusion but uses CWE-98 wording associated with include/require filename control. No exploit details, patch version, vulnerable parameter, or technical advisory content were provided in the source bundle.

Mitigation direction

  • Inventory WordPress sites for the Chronicle theme and installed version.
  • Check AncoraThemes and Patchstack for patched versions or official remediation guidance.
  • Update, replace, or remove the theme if version 1.0 or earlier is present.
  • Prioritize backups and recovery readiness for affected public WordPress sites.

Validation and detection

  • Confirm whether the Chronicle theme is installed on each WordPress instance.
  • Record the installed theme version and compare it to affected versions through 1.0.
  • Review Patchstack and CVE records for updated remediation details.
  • Check web and application logs for unusual file access patterns.
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-27337 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-27337Attack 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
AncoraThemesChronicle - Lifestyle Magazine & Blog WordPress Themechronicle, 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.