LiveActive security incident?Get immediate response
CVE Record

CVE-2026-22362: WordPress Photolia theme <= 1.0.3 - Local File Inclusion vulnerability

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

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-22362 affects the WordPress Photolia theme by axiomthemes through version 1.0.3. A remote, unauthenticated attacker may be able to trigger local file inclusion, potentially exposing sensitive files or affecting site integrity and availability. The issue is rated high severity, but the published CVSS indicates high attack complexity.

Executive priority

Treat as a high-priority WordPress theme risk where Photolia is deployed. Prioritize internet-facing sites and sites handling sensitive data. Business urgency is lower where the theme is absent, but affected sites should be assessed promptly because the potential impact includes data exposure and site compromise.

Technical view

The CVE describes improper control of a filename used in a PHP include/require statement, mapped to CWE-98. The reported impact is PHP local file inclusion in Photolia theme versions up to and including 1.0.3. CVSS 3.1 is 8.1: network accessible, unauthenticated, no user interaction, high complexity, with high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is limited to WordPress sites using the axiomthemes Photolia theme at version 1.0.3 or earlier. The bundle does not identify specific vulnerable files, endpoints, default configurations, or whether inactive installed themes are exploitable.

Exploitation context

The CVE is not listed as CISA KEV in the provided data, and no cited source states active exploitation. The CVSS vector suggests exploitation is remote and unauthenticated but requires high complexity. Public details are limited to the vulnerability classification and affected theme range.

Researcher notes

The public bundle provides severity, CWE, CVSS, and affected version range, but not root-cause code, endpoint details, patch version, or proof of exploitation. Avoid assuming exploitation in the wild. Validation should focus on asset presence, version confirmation, and monitoring vendor/Patchstack updates.

Mitigation direction

  • Identify WordPress sites with the Photolia theme installed.
  • Check the installed Photolia version and compare against <= 1.0.3.
  • Review Patchstack and vendor guidance for an update or official remediation.
  • If no safe update exists, consider disabling or replacing the theme.
  • Monitor web logs for suspicious file-include related requests.

Validation and detection

  • Inventory WordPress themes across production, staging, and backups.
  • Confirm whether Photolia is installed, active, or retained unused.
  • Record Photolia version from WordPress administration or asset inventory.
  • Check the CVE and Patchstack pages for updated affected-version or fix details.
  • Verify remediation by confirming the vulnerable version is no longer present.
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-22362 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-22362Attack 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
axiomthemesPhotoliaphotolia, 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.