LiveActive security incident?Get immediate response
CVE Record

CVE-2026-28097: WordPress Artrium theme <= 1.0.14 - Local File Inclusion vulnerability

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

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-28097 affects the WordPress Artrium theme from ThemeREX through version 1.0.14. It is a local file inclusion issue that may let an unauthenticated remote attacker access or influence files handled by the site. The published CVSS score is high at 8.1.

Executive priority

Treat this as a near-term WordPress exposure review. It is high severity and unauthenticated, but public evidence does not show active exploitation. Prioritize internet-facing WordPress sites using Artrium, especially business-critical or customer-facing sites.

Technical view

The issue is classified as CWE-98: improper control of a filename used in a PHP include/require statement. Public records describe PHP Local File Inclusion in Artrium <= 1.0.14. CVSS indicates network attack vector, no privileges, no user interaction, high complexity, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is likely limited to WordPress sites using the ThemeREX Artrium theme at version 1.0.14 or earlier. The sources do not identify affected hosting configurations, specific vulnerable endpoints, or whether inactive installations are exploitable.

Exploitation context

The CVE record rates exploitation as remote and unauthenticated but high complexity. CISA KEV status is false in the provided data, and no cited source states active exploitation. Public details are limited to the vulnerability class, affected theme, version range, and severity.

Researcher notes

Evidence is sparse. The CVE description and Patchstack entry identify Artrium <= 1.0.14 and LFI, but no patch version, endpoint, proof of concept, or exploitation-in-the-wild claim is cited. The structured affected metadata appears limited, so validate against vendor advisory data.

Mitigation direction

  • Inventory WordPress sites for the Artrium theme and record installed versions.
  • If Artrium is present at <= 1.0.14, check ThemeREX and Patchstack guidance.
  • Apply a vendor-provided fixed version if one is available.
  • Remove or replace the theme where it is not required.
  • Prioritize backups and least-privilege file permissions while awaiting vendor guidance.

Validation and detection

  • Confirm the active WordPress theme and Artrium version on each site.
  • Check whether the site matches the <= 1.0.14 affected range.
  • Review web logs for unusual requests targeting theme files or include paths.
  • Verify remediation against vendor or Patchstack advisory details.
  • Document any sites where no fixed version is available.
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-28097 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-28097Attack 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
ThemeREXArtriumartrium, 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.