LiveActive security incident?Get immediate response
CVE Record

CVE-2026-22401: WordPress Freshio theme <= 2.4.2 - Local File Inclusion vulnerability

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

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-22401 affects the WordPress Freshio theme through version 2.4.2. A user with some site privileges may be able to make the theme include unintended local files, potentially exposing data or impacting site integrity. No source provided indicates active exploitation.

Executive priority

Treat as a high-priority WordPress theme exposure, especially for public sites with multiple user accounts. Prioritize inventory and vendor update checks now; escalate if a patch, exploit evidence, or active exploitation reporting appears.

Technical view

The issue is classified as CWE-98: improper control of filename in PHP include/require logic. The CVSS 3.1 score is 7.5 with AV:N/AC:H/PR:L/UI:N and high confidentiality, integrity, and availability impact. Public details do not identify the vulnerable endpoint, proof of concept, or fixed version.

Likely exposure

Exposure is likely limited to WordPress sites running the pavothemes Freshio theme at version 2.4.2 or earlier. The CVSS vector indicates exploitation requires low privileges, so sites with untrusted or numerous authenticated users face higher risk.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of exploitation in the wild. Exploitation is described as network-accessible but high complexity and requiring low privileges, with no user interaction.

Researcher notes

Evidence is limited. The CVE and Patchstack entry identify Freshio through 2.4.2 as affected, but the bundle does not include a patch version, vulnerable parameter, exploit details, or active exploitation evidence. The affected-version metadata appears sparse, so validate against vendor and Patchstack updates.

Mitigation direction

  • Inventory WordPress sites using the Freshio theme.
  • Identify Freshio versions at or below 2.4.2.
  • Check pavothemes, Patchstack, and CVE guidance for a fixed release.
  • Apply the vendor-provided update when available.
  • Disable or replace Freshio where risk is unacceptable.
  • Limit unnecessary WordPress user accounts and privileges.

Validation and detection

  • Confirm whether Freshio is installed on each WordPress site.
  • Record the installed Freshio version and compare to 2.4.2.
  • Review security sources for any newly published fixed version.
  • Use authenticated vulnerability scanning where supported.
  • Review logs for unusual authenticated file-access behavior.
  • Track remediation status per affected site.
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-22401 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
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:L/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
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H1.65.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:H/PR:L/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
pavothemesFreshiofreshio, 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.