LiveActive security incident?Get immediate response
CVE Record

CVE-2026-22363: WordPress Rhodos theme <= 1.3.3 - Local File Inclusion vulnerability

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

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-22363 affects the WordPress Rhodos theme through version 1.3.3. It is a local file inclusion issue that could let an unauthenticated attacker cause the site to include unintended files. The published severity is high, but the attack complexity is rated high.

Executive priority

Treat as a high-priority WordPress exposure review, especially for public sites using Rhodos. Do not assume compromise from current evidence, but identify affected sites quickly and watch for vendor remediation because potential impact spans data exposure, site modification, and service disruption.

Technical view

The CVE describes improper control of filenames in a PHP include/require statement, mapped to CWE-98. Affected product is axiomthemes Rhodos, through version 1.3.3. CVSS 3.1 is 8.1: network-accessible, unauthenticated, no user interaction, high confidentiality, integrity, and availability impact, with high attack complexity.

Likely exposure

Exposure is likely limited to WordPress sites using the Rhodos theme at version 1.3.3 or earlier. The source bundle does not confirm whether inactive installed themes are exploitable, so prioritize sites where Rhodos is active or present.

Exploitation context

No provided source states active exploitation, and the CVE is not marked KEV. The vulnerability is remotely reachable and unauthenticated per CVSS, but exploitation is rated high complexity. Public details in the provided sources are limited.

Researcher notes

The record contains limited technical detail beyond CWE-98, LFI wording, affected version range, and CVSS vector. There is no cited proof of concept, exploitation claim, or fixed version in the provided bundle. Validate against the Patchstack entry and vendor guidance before making remediation assertions.

Mitigation direction

  • Inventory WordPress sites for the Rhodos theme and version.
  • Prioritize sites running Rhodos 1.3.3 or earlier.
  • Check AxiomThemes, Patchstack, and CVE updates for vendor remediation guidance.
  • If no fix is available, consider disabling or removing Rhodos where operationally feasible.
  • Restrict administrative access and apply normal WordPress hardening controls.

Validation and detection

  • Confirm whether Rhodos is installed, active, and at or below version 1.3.3.
  • Review vendor and Patchstack advisories for any fixed version or workaround.
  • Check web logs for unusual file access or include-related errors.
  • Verify backups and recovery procedures for affected WordPress sites.
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-22363 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-22363Attack 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
axiomthemesRhodosrhodos, 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.