LiveActive security incident?Get immediate response
CVE Record

CVE-2026-27997: WordPress Maxify theme <= 1.0.16 - Local File Inclusion vulnerability

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

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-27997 affects the WordPress Maxify theme from ThemeREX through version 1.0.16. It is a local file inclusion issue that could let an unauthenticated remote attacker access or affect sensitive server-side files. The CVSS score is 8.1 high, but exploitation is rated high complexity and no active exploitation is cited in the provided sources.

Executive priority

Prioritize review for public WordPress sites using Maxify. The issue is high severity and unauthenticated, but available sources do not show active exploitation or a named patch. Business urgency is highest where Maxify <=1.0.16 is deployed on internet-facing production sites.

Technical view

The flaw is improper control of a filename used in PHP include/require logic, tracked as CWE-98. The CVSS vector is AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H. Sources describe PHP Local File Inclusion in Maxify <=1.0.16. The record does not provide exploit details or a confirmed fixed version.

Likely exposure

Exposure is limited to WordPress sites using the ThemeREX Maxify theme at version 1.0.16 or earlier. Sites not using this theme are not indicated as affected. Confirm whether the theme is installed, active, or present on disk, because inactive themes can still increase operational risk.

Exploitation context

The CVSS vector indicates unauthenticated network reachability with no user interaction, but high attack complexity. The provided data does not cite CISA KEV listing or any confirmed active exploitation. Treat as important for internet-facing WordPress assets, especially where the vulnerable theme is installed.

Researcher notes

Evidence is limited to the CVE record and Patchstack database entry. The affected range is stated as Maxify through <=1.0.16. No exploit code, indicators of active exploitation, or fixed version are provided in the source bundle. Avoid assuming broader ThemeREX product impact without additional vendor confirmation.

Mitigation direction

  • Inventory WordPress sites for the ThemeREX Maxify theme.
  • Check installed Maxify versions and flag 1.0.16 or earlier.
  • Review ThemeREX and Patchstack guidance for an update or official workaround.
  • If no fix is available, consider disabling or removing the theme.
  • Restrict administrative access and keep WordPress, themes, and plugins current.

Validation and detection

  • Confirm whether Maxify is installed, active, or present on each WordPress host.
  • Record the exact Maxify version from trusted administrative or file inventory sources.
  • Review web and application logs for suspicious file path or include-related requests.
  • Verify remediation by confirming the vulnerable theme version is absent or updated.
  • Monitor the CVE and Patchstack entries for updated fix information.
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-27997 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-27997Attack 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
ThemeREXMaxifymaxify, 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.