LiveActive security incident?Get immediate response
CVE Record

CVE-2026-22408: WordPress Justicia theme <= 1.2 - Local File Inclusion vulnerability

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Mikado-Themes Justicia justicia allows PHP Local File Inclusion.This issue affects Justicia: from n/a through <= 1.2.

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-22408 affects the WordPress Justicia theme through version 1.2. It is a local file inclusion issue that could let an unauthenticated network attacker affect confidentiality, integrity, and availability. The CVSS score is high, but the attack complexity is high and no active exploitation is cited in the provided sources.

Executive priority

Prioritize identification and containment for any business-critical WordPress site using Justicia. The issue is high severity with unauthenticated remote reachability, but current public sources do not show known exploitation or a named patch.

Technical view

The CVE describes improper control of filenames in PHP include/require handling in Mikado-Themes Justicia. The listed vector is AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H with CVSS 8.1. Public details do not identify the vulnerable parameter, exploit method, or a confirmed fixed version.

Likely exposure

Exposure is likely limited to WordPress sites with the Justicia theme installed at version 1.2 or earlier. Internet-facing WordPress deployments are the primary concern. Sites not using this theme are not indicated as affected by the provided sources.

Exploitation context

The CVE vector indicates remote, unauthenticated exploitation with no user interaction, but high attack complexity. The issue is not listed in CISA KEV, and the provided sources do not claim active exploitation or public exploit availability.

Researcher notes

The source data has limited technical detail and an affected-version inconsistency: the narrative says through 1.2, while the affected object lists version 0 with defaultStatus unaffected. Use the CVE description and Patchstack entry for scoping, and re-check vendor data before final remediation decisions.

Mitigation direction

  • Inventory WordPress sites for the Justicia theme and version.
  • If Justicia is version 1.2 or earlier, treat the site as exposed.
  • Check Mikado-Themes and Patchstack guidance for a fixed release or vendor workaround.
  • If no fix is available, consider deactivating or replacing the theme.
  • Prioritize backups and recovery readiness for affected WordPress sites.

Validation and detection

  • Confirm whether Justicia is installed on each WordPress instance.
  • Record the installed theme version and compare it to affected versions through 1.2.
  • Review vendor and Patchstack pages for updated remediation details.
  • Check web server and WordPress logs for unusual file access patterns.
  • Document compensating controls if the theme cannot be removed promptly.
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-22408 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-22408Attack 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
Mikado-ThemesJusticiajusticia, 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.